Re: LC_COLLATE=es_MX in PgSQL 7.3.2

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: alvarezp(at)octavio(dot)ods(dot)org
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: LC_COLLATE=es_MX in PgSQL 7.3.2
Date: 2003-06-13 01:09:40
Message-ID: 22112.1055466580@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Octavio Alvarez" <alvarezp(at)octavio(dot)ods(dot)org> writes:
> I don't know if detection of which keys are equal (in this case
> octav=OCTAV=OCTAV) should be made by PostgreSQL or libc. I also don't know
> if I am wrong assuming octav=OCTAV. For alphabetic sorting, it should be
> case insensitive.

I believe that the usual locale definitions set things up so that
strings of different case are not "equal", but case differences are
the last tiebreaker when sorting. So "octav" sorts before "OCTAV"
but after everything else that's less than "OCTAV".

I haven't studied your results to see if they are consistent with
that viewpoint, but I'm really not ready to believe that Postgres
is sorting in a way that's not what the active locale says to do.
We have not heard such a report before. (We have, on the other
hand, heard from lots of people who were surprised at the properties
of their default locale ...)

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2003-06-13 01:38:42 Re: More VACUUM output?
Previous Message Ernest E Vogelsinger 2003-06-13 00:56:01 Re: Query planner question