Best practices for moving UTF8 databases

From: Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com>
To: PG-General Mailing List <pgsql-general(at)postgresql(dot)org>
Subject: Best practices for moving UTF8 databases
Date: 2009-07-12 11:19:50
Message-ID: e373d31e0907120419t5c96d6dk829940dac1fbb821@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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?

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Sam Mason 2009-07-12 11:36:17 Re: INSERT only unique records
Previous Message Joe Conway 2009-07-12 09:51:39 Re: BUG #4916: wish: more statistical functions (median, percentiles etc)