Re: LATIN2 'bssz' and 'bszsz' fails on unique index - Mailing list pgsql-bugs

From Tom Lane
Subject Re: LATIN2 'bssz' and 'bszsz' fails on unique index
Date
Msg-id 24642.1085121261@sss.pgh.pa.us
Whole thread Raw
In response to LATIN2 'bssz' and 'bszsz' fails on unique index  (Sün <sun@true.hu>)
Responses Re: LATIN2 'bssz' and 'bszsz' fails on unique index
List pgsql-bugs
Sün <sun@true.hu> writes:
> If you use Latin2 encoding, you can not have 'bssz' and 'bszsz' in an
> unique column in the same time.

AFAICS this means that your locale definition considers these strings
equal.

It is possible that the real problem comes from using an encoding that's
not compatible with what the locale setting expects.  Locales generally
do require a specific character set encoding, though this is poorly
documented :-(
        regards, tom lane


pgsql-bugs by date:

Previous
From: Sün
Date:
Subject: LATIN2 'bssz' and 'bszsz' fails on unique index
Next
From: Neil Conway
Date:
Subject: Re: int4, int8, real ....division...