| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Роман Литовченко <roman(dot)lytovchenko(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15285: Query used index over field with ICU collation in some cases wrongly return 0 rows |
| Date: | 2018-07-19 23:26:49 |
| Message-ID: | CAH2-Wzkiue6PQzneBJsuDnYdUVMa5jnevVJXXkV3hR0oboOSbQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Jul 19, 2018 at 9:44 AM, Peter Geoghegan <pg(at)bowt(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2018-07-20 04:52:48 | BUG #15286: BEFORE or AFTER not working while adding values for existing enums |
| Previous Message | Jeremy Schneider | 2018-07-19 23:17:44 | Fwd: BUG #15182: Canceling authentication due to timeout aka Denial of Service Attack |