Re: [HACKERS] problem with casts dump/restore

From: "John Hansen" <john(at)geeknet(dot)com(dot)au>
To: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>, <pgadmin-hackers(at)postgresql(dot)org>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] problem with casts dump/restore
Date: 2005-01-11 20:48:28
Message-ID: 5066E5A966339E42AA04BA10BA706AE5622A@rodrick.geeknet.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers pgsql-hackers

I have not had time to install RC4 / RC5 yet, but have anyone tried this:

Createdb -Eunicode test
Psql test -c 'create table foo (bar text);

Then connect using libpq, and in your software application (C) pqexec something like:

'set client_encoding=ascii'
Insert into foo(bar) values('some text with accented characters');

Pg_dump was never able to dump that in a format that it was possible to restore with psql.
I usually had to manually edit the dump, and issue set client_encoding=ascii; set client_encoding=unicode; before and after the entries that was inserted with ascii encoding.

We're talking a table with millions of entries where only a few had been inserted using ascii encoding.

If someone could test it before release it would be good, unfortunately I will not have the time to do so myself.

Kind Regards,

John

Browse pgadmin-hackers by date

  From Date Subject
Next Message Andreas Pflug 2005-01-11 22:19:09 Re: pgAdmin on Mac OS X
Previous Message Tom Lane 2005-01-11 18:53:37 Re: problem with casts dump/restore

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-01-11 21:51:05 Re: Verbosity of column definition mismatch error
Previous Message Merlin Moncure 2005-01-11 20:45:29 Re: problem with casts dump/restore