From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com> |
Subject: | Re: Best practices for moving UTF8 databases |
Date: | 2009-07-13 14:45:35 |
Message-ID: | 200907131645.36439.andres@anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sunday 12 July 2009 13:19:50 Phoenix Kiula wrote:
> Hi. I *always* get an error moving my current fully utf-8 database
> data into a new DB.
>
> My server has the version 8.3 with a five year old DB. Everything, all
> collation, LC_LOCALE etc are all utf8.
>
> When I install a new Postgresql 8.4 on my home Mac OSX machine (after
> losing some hair) I set everything about a new database to be utf8. At
> least anything I could see in PgAdmin.
>
> But when I pull in the data dump from the server I always see that
> error from the utf8 mismatch and such.
>
> So, my question. What is a good way to make sure that error does NOT
> occur? I simply wish to replicate the server database on another PG
> installation. What should one do?
What is the _exact_ error you get? During which statement?
Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Tim Landscheidt | 2009-07-13 14:48:39 | PostgreSQL 8.4 packages for Fedora 11? |
Previous Message | Alvaro Herrera | 2009-07-13 14:40:50 | Re: uuid_hash declaration |