Bruce Momjian <[EMAIL PROTECTED]> writes:
> Pavel Stehule wrote:
>> I send my first patch for PostgreSQL - maybe ugly patch. This patch
>> generate on top of dump file line with setting of current encoding. Its
>> useful for languages like czech with more than one wide used encoding.
>> We need informations about used encoding.
> I found this patch intersting. How do we deal with restoring a database
> with a different encoding from the one dumped. Does having SET at the
> top help? (Also, we use diff -c.)
Yes, the SET should help; it will result in character encoding
translation to whatever the database encoding is. This has been
discussed before, IIRC.
I was planning to commit this patch (perhaps after cleanup, haven't
looked at it yet) but it's not got to the top of the todo queue...
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
