From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Johann Spies <jspies(at)sun(dot)ac(dot)za> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Problem restoring a dump |
Date: | 2011-09-13 20:07:48 |
Message-ID: | 1315944468.5302.0.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Tue, 2011-09-13 at 14:47 +0200, 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?
>
No, you can't. You need to create a new one with the good encoding.
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-09-13 20:22:44 | Re: exit code 139 performing initdb (pg 9.1 on linux) |
Previous Message | Tom Lane | 2011-09-13 19:41:10 | Re: exit code 139 performing initdb (pg 9.1 on linux) |