Tom Lane wrote:
> Mage <mage@mage.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
