Best practices for moving UTF8 databases - Mailing list pgsql-general

From Phoenix Kiula
Subject Best practices for moving UTF8 databases
Date
Msg-id e373d31e0907120419t5c96d6dk829940dac1fbb821@mail.gmail.com
Whole thread Raw
Responses Re: Best practices for moving UTF8 databases
Re: Best practices for moving UTF8 databases
List pgsql-general
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?

pgsql-general by date:

Previous
From: Roy Walter
Date:
Subject: xpath() subquery for empty array
Next
From: Sam Mason
Date:
Subject: Re: INSERT only unique records