Re: create index regression fail - Mailing list pgsql-hackers

From Jaime Casanova
Subject Re: create index regression fail
Date
Msg-id CAJKUy5gYAQHV_Yzqg08euAqOhYLkiNMra8r23VwTMPBU=geJrw@mail.gmail.com
Whole thread Raw
In response to Re: create index regression fail  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: create index regression fail  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
On Thu, Jan 12, 2012 at 1:59 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Jaime Casanova <jaime@2ndquadrant.com> writes:
>> the query where the regression fails is:
>
>> SELECT count(*) FROM dupindexcols
>>   WHERE f1 > 'LX' and id < 1000 and f1 ~<~ 'YX';
>
>> my first theory was that it was because some locale because mine is
>> es_EC.UTF-8 but the content of the table doesn't justify that,
>
> [ experiments... ]  Looks like you're wrong about that.  In ec_EC locale
> on my machine, the test accepts these rows that are not accepted in C
> locale:
>
>  223 | LLKAAA
>  738 | LLEAAA
>

oh! i remember now a thread where we talk about glibc not doing the
right thing about this:
http://archives.postgresql.org/message-id/20081215160148.GF4067@alvh.no-ip.org

an update to that post would be that in that time CH and LL where
independent letters but sorted as if they weren't, now they both were
degraded to be a combination of two letters.

--
Jaime Casanova         www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: pgbench post-connection command
Next
From: "Kevin Grittner"
Date:
Subject: Re: Remembering bug #6123