User-Agent: Microsoft-Entourage/11.4.0.080122
Date: Mon, 11 May 2009 08:28:45 +0200
Subject: Re: Distinct oddity
From: Maximilian Tyrtania <maximilian.tyrtania@onlinehome.de>
To: Alvaro Herrera <alvherre@commandprompt.com>
CC: <pgsql-sql@postgresql.org>
Message-ID: <C62D923D.35F9B%maximilian.tyrtania@onlinehome.de>
Thread-Topic: [SQL] Distinct oddity
Thread-Index: AcnSAbwj+nwqGj30Ed6oSgAjMt4/tA==
In-Reply-To: <20090510025822.GD5365@alvh.no-ip.org>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

am 10.05.2009 4:58 Uhr schrieb Alvaro Herrera unter
alvherre@commandprompt.com:

>>> and what locale are you running in?
>> 
>>  lc_collate                      | de_DE
>> | Shows the collation order locale.
>>  lc_ctype                        | de_DE
>> | Shows the character classification and case conversion locale.
>> 
>> The encoding is UTF-8.
> 
> Note that the de_DE locale uses Latin9 encoding, which is incompatible
> with UTF8. 

Ah, good catch.

> I'd try checking if the problem is reproducible in
> de_DE.utf8 (you need to create a new database for testing, obviously).

Wait a minute. I need to re- initdb with de_DE.UTF-8, don't I?

> If it's not, then the incompatible locale definition is causing the
> problem.

I'll try that, thanks.

M