Fri Jul 29 15:54:07 PDT 2005
- Previous message: [Slony1-commit] By dpage: Attached is a patch that refactors slon a tiny bit, by
- Next message: [Slony1-commit] By cbbrowne: Remove spurious comma in SET DROP TABLE example
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Log Message:
-----------
Add FAQ entry on the multibyte column bug...
Modified Files:
--------------
slony1-engine/doc/adminguide:
faq.sgml (r1.41 -> r1.42)
-------------- next part --------------
Index: faq.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/faq.sgml,v
retrieving revision 1.41
retrieving revision 1.42
diff -Ldoc/adminguide/faq.sgml -Ldoc/adminguide/faq.sgml -u -w -r1.41 -r1.42
--- doc/adminguide/faq.sgml
+++ doc/adminguide/faq.sgml
@@ -1590,6 +1590,19 @@
comfortable with &postgres; and &slony1; that you are prepared to hack
pretty heavily with the code. </para> </answer>
</qandaentry>
+
+<qandaentry>
+<question> <para> I am finding some multibyte columns (Unicode, Big5)
+are being truncated. Why? </para> </question>
+
+<answer> <para> This was a bug present until a little after &slony1;
+version 1.1.0; the way in which columns were being captured by the
+<function>logtrigger()</function> function could clip off the last
+byte of a column represented in a multibyte format. Check to see that
+your version of <filename>src/backend/slony1_funcs.c</filename> is
+1.34 or better; the patch was introduced in CVS version 1.34 of that
+file. </para> </answer>
+</qandaentry>
</qandaset>
<!-- Keep this comment at the end of the file Local variables:
- Previous message: [Slony1-commit] By dpage: Attached is a patch that refactors slon a tiny bit, by
- Next message: [Slony1-commit] By cbbrowne: Remove spurious comma in SET DROP TABLE example
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list