Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #15285: Query used index over field with ICU collation insome cases wrongly return 0 rows - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: BUG #15285: Query used index over field with ICU collation insome cases wrongly return 0 rows
Date
Msg-id CAH2-Wzkiue6PQzneBJsuDnYdUVMa5jnevVJXXkV3hR0oboOSbQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #15285: Query used index over field with ICU collation insome cases wrongly return 0 rows  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: BUG #15285: Query used index over field with ICU collation insome cases wrongly return 0 rows  (Thomas Munro <thomas.munro@enterprisedb.com>)
List pgsql-bugs
Tree view 
On Thu, Jul 19, 2018 at 9:44 AM, Peter Geoghegan <pg@bowt.ie> wrote:
> It appears that the main support function 1 routine disagrees with the
> CREATE INDEX sort order, which is wrong. I'll try to isolate the
> problem a bit further.

As far as I can tell, this is an ICU bug. ucol_strcollUTF8() is buggy
with this digitslast collation, which ucol_nextSortKeyPart() fails to
be bug-compatible with. Other similar customized collations (e.g.
'en-u-kf-upper') work fine. (Ugh, that's familiar in an unpleasant
way.)

I'm using libicu60. What version are you using, Roman?

I tried to find something that matches this on the ICU bug tracker.
This might be a match: https://ssl.icu-project.org/trac/ticket/12518

-- 
Peter Geoghegan

pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: BUG #15285: Query used index over field with ICU collation insome cases wrongly return 0 rows
Next
From: PG Bug reporting form
Date:
Subject: BUG #15286: BEFORE or AFTER not working while adding values forexisting enums