Message-ID: <48C4F322.1050905@gmx.net>
Date: Mon, 08 Sep 2008 12:40:50 +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@gmx.de
CC: pgsql-admin@postgresql.org
Subject: Re: server/db encoding (mix) issues
References: <20080903102701.205580@gmx.net> <48BFE6B9.7030103@gmx.net>
	<20080908085758.36590@gmx.net>
In-Reply-To: <20080908085758.36590@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Jan-Peter.Seifert@gmx.de wrote:
> Well - I did setup two instances of 8.3.3 on an Ubuntu 7.10 system last week - both under a different user account. I set the locale for each account in the .bashrcs ("export LANG=de_DE" and "export LANG=de_DE.UTF-8" respectively). After that I ran initdb ("initdb --encoding='LATIN1' -W -A md5 -D $PGDATA" and "initdb --encoding='UTF8' -W -A md5 -D $PGDATA"(?)). I'm not sure whether I specified the server encoding for the UTF8-instance though. Did I make something wrong?

Not really, but I suggest you forget about the environment settings and 
forget about the --encoding option and just use the --locale option of 
initdb to set the locale settings.

> However, when I try to create an UTF-8 db in the LATIN1 server or an LATIN1 db in the UTF-8 server I get the error that the db encoding does not match the server locale and that the LC_TYPE-Locale requires the encoding of the server. Before that I thought it just fails because there is no locale with the name LATIN1 in windows. Are those additional encoding checks in v8.3.3 or had they been put in place with v8.3.1 already? 

They have existed since 8.3.0.