Log Message:
-----------
Bug #1608 reported problems that can arise if client/server character
encodings do not match.  Adding this to documentation.

Tags:
----
REL_1_2_STABLE

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        prerequisites.sgml (r1.26 -> r1.26.2.1)

-------------- next part --------------
Index: prerequisites.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/prerequisites.sgml,v
retrieving revision 1.26
retrieving revision 1.26.2.1
diff -Ldoc/adminguide/prerequisites.sgml -Ldoc/adminguide/prerequisites.sgml -u -w -r1.26 -r1.26.2.1
--- doc/adminguide/prerequisites.sgml
+++ doc/adminguide/prerequisites.sgml
@@ -131,6 +131,16 @@
 invalid encodings.  This can lead to <link linkend="faqunicode">
 replication problems.</link> </para>
 
+<para> Note also that if the client encoding (configured assortedly in
+<filename>postgresql.conf</filename>, parameter
+<envar>client_encoding</envar>, or via the
+<application>psql</application> <command>\encoding </command> command,
+or the <application>psql</application> internal variable
+<envar>ENCODING</envar>) varies from the server encoding, this
+mismatch may lead to &slony1; being unable to replicate those
+characters supported by the client encoding but not by the server
+encoding. </para>
+
 </sect2>
 
 <sect2 id="times">