From: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
---|---|
To: | Johann Spies <jspies(at)sun(dot)ac(dot)za>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Problem restoring a dump |
Date: | 2011-09-14 01:56:27 |
Message-ID: | 4E7009CB.9050807@ringerc.id.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 09/13/2011 08:47 PM, Johann Spies wrote:
> Thanks Giulio and Gabriele,
>
>> as Giulio pointed out, it seems like the destination database is in
>> LATIN1 encoding, rather than UTF8. Could you please confirm this?
> That was the case. I deleted one of the databases and recreated it with
> as a UTF-8 encoded database and the import went well.
>
> Question: Can I change the encoding system of an existing database? If
> so, how?
>
You can re-encode a dump (see pg_dump's -E flag) then reload it into a
new database with the new encoding. This will only work if the source
database contains only characters that exist in the target encoding.
You can't change the encoding of a database in-place.
--
Craig Ringer
--
Craig Ringer
From | Date | Subject | |
---|---|---|---|
Next Message | Mokhtary, Mandana | 2011-09-14 05:37:18 | encoding problem |
Previous Message | Craig Ringer | 2011-09-14 01:53:00 | Re: pg_upgrade --link |