Log Message:
-----------
Mention best practices with regards to time zone handling

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        prerequisites.sgml (r1.14 -> r1.15)
        bestpractices.sgml (r1.4 -> r1.5)

-------------- next part --------------
Index: prerequisites.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/prerequisites.sgml,v
retrieving revision 1.14
retrieving revision 1.15
diff -Ldoc/adminguide/prerequisites.sgml -Ldoc/adminguide/prerequisites.sgml -u -w -r1.14 -r1.15
--- doc/adminguide/prerequisites.sgml
+++ doc/adminguide/prerequisites.sgml
@@ -104,7 +104,7 @@
 
 </sect2>
 
-<sect2>
+<sect2 id="times">
 <title> Time Synchronization</title>
 
 <para> All the servers used within the replication cluster need to
Index: bestpractices.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/bestpractices.sgml,v
retrieving revision 1.4
retrieving revision 1.5
diff -Ldoc/adminguide/bestpractices.sgml -Ldoc/adminguide/bestpractices.sgml -u -w -r1.4 -r1.5
--- doc/adminguide/bestpractices.sgml
+++ doc/adminguide/bestpractices.sgml
@@ -39,6 +39,24 @@
 
 </listitem>
 
+<listitem><para> Principle: Use an unambiguous, stable time zone such
+as UTC or GMT. </para>
+
+<para> Users have run into problems when their system uses a time zone
+that &postgres; was unable to recognize such as CUT0 or WST.  It is
+necessary that you use a timezone that &postgres; can recognize
+correctly.
+</para>
+
+<para> It is furthermore preferable to use a time zone where times do
+not shift around due to Daylight Savings Time. </para>
+
+<para> The <quote>geographically unbiased</quote> choice seems to be
+<command><envar>TZ</envar>=UTC</command> or
+<command><envar>TZ</envar>=GMT</command>. </para>  
+
+<para> See also <xref linkend="times">.  </listitem>
+
 <listitem><para> Principle: Long running transactions are Evil </para>
 
 <para> The FAQ has an entry on <link linkend="pglistenerfull"> growth