Re: [PATCHES] client_encoding in dump file

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz>
Cc: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [PATCHES] client_encoding in dump file
Date: 2004-02-11 22:20:06
Message-ID: 200402112220.i1BMK6t22977@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Pavel Stehule wrote:
> Hello
>
> 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.)

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-02-11 22:20:12 Circular-freelist bug is still there
Previous Message scott.marlowe 2004-02-11 22:16:24 Re: How can I have 2 completely seperated databases in

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2004-02-11 22:22:35 Re: psql prompts with invisible characters
Previous Message Bruce Momjian 2004-02-11 21:47:09 Thread redesign