Re: UNIQUE INDEX difference between 7.2 and 7.3 - Mailing list pgsql-bugs

From Kevin Houle
Subject Re: UNIQUE INDEX difference between 7.2 and 7.3
Date
Msg-id 5170000.1060707300@discus.blue.cert.org
Whole thread Raw
In response to Re: UNIQUE INDEX difference between 7.2 and 7.3  (Stephan Szabo <sszabo@megazone.bigpanda.com>)
List pgsql-bugs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- --On Tuesday, August 12, 2003 08:47:08 AM -0700 Stephan Szabo
<sszabo@megazone
.bigpanda.com> wrote:

> On Tue, 12 Aug 2003, Kevin Houle wrote:
>
>> >> There is an email attachment (md5: 5cc780da645df9516235d43d1cf1e8b5)
>> >> which contains a file with two SQL INSERT commands to insert two rows
>> >> into a test table. The table should look like this:
>> >>
>> >>   CREATE TABLE tbl_test (
>> >>     testcol text,
>> >>     unique (testcol)
>> >>   );
>> >>
>> >> The databases in my testing are using SQL_ASCII encoding.
>> >
>> > I don't receive an error on my 7.3.4 system, what locale is the
>> > database initialized in?
>>
>> I'm using defaults, so on RH9 it is:
>>
>>   /var/lib/pgsql/initdb.i18n:
>>    LANG="en_US.UTF-8"
>
> Okay, I see it with en_US.UTF-8, but not with C locale, nor with
> en_US or en_US.iso885915.  It looks like the comparison rules are
> different between the locales (and I'm not sure if SQL_ASCII encoding
> and a UTF8 locale makes sense in practice).

Good point. I don't see the behavior with locale=en_US, either. I'll
use that as a work-around. Probably a few other RH9 users out there
getting into the same situation using the PGDG and Red Hat RPMS.

I appreciate your taking the time to look at this.

Cheers,
Kevin


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/ORu7u/NTC+XTbEkRAiwlAKCkqpPyQX7mLXx5iKMAAf7v03t6JwCfUvIB
qL8Xz60qXwigV/LnzkGTM8M=
=Q0iV
-----END PGP SIGNATURE-----

pgsql-bugs by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: UNIQUE INDEX difference between 7.2 and 7.3
Next
From: Tom Lane
Date:
Subject: Re: UNIQUE INDEX difference between 7.2 and 7.3