Re: Problem restoring a dump - Mailing list pgsql-admin

From Craig Ringer
Subject Re: Problem restoring a dump
Date
Msg-id 4E7009CB.9050807@ringerc.id.au
Whole thread Raw
In response to Re: Problem restoring a dump  (Johann Spies <jspies@sun.ac.za>)
Responses Re: Problem restoring a dump
List 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

pgsql-admin by date:

Previous
From: Craig Ringer
Date:
Subject: Re: pg_upgrade --link
Next
From: "Mokhtary, Mandana"
Date:
Subject: encoding problem