Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5);

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Reko Turja <reko(dot)turja(at)liukuma(dot)net>
Cc: PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5);
Date: 2016-03-25 20:15:25
Message-ID: CAEepm=1bvR3Dzgnh7_sfOUr=zsfNvgs0qMOejaonk=Fzq1ZXeg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Mar 25, 2016 at 3:02 AM, Reko Turja <reko(dot)turja(at)liukuma(dot)net> wrote:
> Tom Lane wrote:
>
>> Indeed. To try to put some scope on the problem, I made an idiot little
>> program that just generates some random UTF8 strings and sees whether
>> strcoll and strxfrm sort them alike. Attached are that program, a even
>> more idiot little shell script that runs it over all available UTF8
>> locales, and the results on my RHEL6 box. While de_DE seems to be the
>> worst-broken locale, it's far from the only one.
>>
>> Please try this on as many platforms as you can get hold of ...
>
>
> Platform - FreeBSD 10.2, everything built from source using clang:
>
> [all good]

FWIW I tried this on FreeBSD 11.0-CURRENT (the version currently in
development which contains a new collation implementation that deals
with Unicode) and it didn't look good so I reported that over here:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208266

--
Thomas Munro
http://www.enterprisedb.com

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2016-03-26 12:39:42 Re: Breakage with VACUUM ANALYSE + partitions
Previous Message Andres Freund 2016-03-25 16:49:27 Re: Breakage with VACUUM ANALYSE + partitions