Message-ID: <48BFE6B9.7030103@gmx.net>
Date: Thu, 04 Sep 2008 16:46:33 +0300
From: Peter Eisentraut <peter_e@gmx.net>
User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707)
MIME-Version: 1.0
To: Jan-Peter Seifert <Jan-Peter.Seifert@gmx.de>
CC: Postgres <pgsql-admin@postgresql.org>
Subject: Re: server/db encoding (mix) issues
References: <20080903102701.205580@gmx.net>
In-Reply-To: <20080903102701.205580@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Jan-Peter Seifert wrote:
> we have a mix of older software still using LATIN1 as db encoding and the psqlODBC-drivers (ANSI) and newer software using UTF8 as db encoding. As running two server instances would use up more resources(?) than just one we'd like to have all dbs in one cluster. Which cons against this solution are there? Which operating system locale should be used then? C locale is recommended in the docs - also because of better performance. However, the language of the software is not English but German - so shouldn't there be problems with sorting German Umlauts etc. correctly etc.? Which encoding should the server have - UTF8/Unicode or LATIN1? BTW which is the correct locale for LATIN1 and German (de_DE (my guess) or de_DE@euro (which seems to be for LATIN9)). Using SQL_ASCII doesn't seem to be a wise choice. Are there no problems when connecting with psqlODBC-ANSI drivers if the server encoding is UTF8/Unicode? I'd be happy if you could enlighten me a bit.

Set your locale to de_DE.utf8 and use UTF8 as server encoding.

I would be interested to know where the documentation "recommends" using 
the C locale.  That would certainly not be reasonable for many uses.