From: | Mage <mage(at)mage(dot)hu> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: upgrading to 8.3, utf-8 and latin2 locale problem |
Date: | 2008-04-01 18:51:03 |
Message-ID: | 47F28417.30004@mage.hu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
> Mage <mage(at)mage(dot)hu> writes:
>
>> We would like to upgrade from 8.1 to 8.3. We have UTF-8 and LATIN2
>> databases. Any idea?
>>
>
> If you were running with a non-C database locale, that was always
> broken in 8.1, and you are very fortunate not to have stumbled across
> any of the failure cases.
>
> You can either standardize on UTF8 for all your databases (note that
> this does not stop your *clients* from using LATIN2 if they want),
> or use C locale which will work equally poorly with all encodings ;-)
>
If it were up to me, I'd never use LATIN2. I switched to unicode years ago.
Some of our databases don't belong to me and I can't modify their clients.
What is the proper use of "create database xxxx encoding = 'yyy'" in
postgresql 8.3? If I understand You, I should avoid it totally, and
convert every affected database dumps to UTF-8, load them and use "alter
database xxx set client_encoding = 'latin2'". Is it right?
Mage
From | Date | Subject | |
---|---|---|---|
Next Message | Tony Caduto | 2008-04-01 18:53:30 | Re: Getting weird pg_tblspc error, has anyone seen this before? |
Previous Message | Tom Lane | 2008-04-01 18:15:51 | Re: upgrading to 8.3, utf-8 and latin2 locale problem |