Re: [PATCHES] client_encoding in dump file

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] client_encoding in dump file
Date: 2004-02-11 23:29:09
Message-ID: 24153.1076542149@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gavin Sherry 2004-02-11 23:29:20 Re: SET WITHOUT OIDS and VACUUM badness?
Previous Message Bruce Momjian 2004-02-11 23:25:19 Re: [BUGS] Bug in pg_autovacuum ?

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2004-02-12 02:30:34 Forwarded PITR patch
Previous Message Bruce Momjian 2004-02-11 22:22:35 Re: psql prompts with invisible characters