Re: Best practices for moving UTF8 databases

From: "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "Phoenix Kiula *EXTERN*" <phoenix(dot)kiula(at)gmail(dot)com>, "PG-General Mailing List" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Best practices for moving UTF8 databases
Date: 2009-07-13 08:31:17
Message-ID: D960CB61B694CF459DCFB4B0128514C203937E1E@exadv11.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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?

Improve PostgreSQL so that there are no more loopholes how you can
enter incorrect data :^(

8.3 is about one and a half years old, so your database must have
oribinated with an older release. Correctness checks have improved
considerably over the years.

What you will have to do it track down the rows containing incorrect data
and fix them.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message IVO GELOV 2009-07-13 08:42:01 Re: Rule acting as REPLACE INTO behave strange
Previous Message Grzegorz Jaśkiewicz 2009-07-13 08:17:15 Re: Re: [BUGS] BUG #4916: wish: more statistical functions (median, percentiles etc)