Re: BUG #15285: Query used index over field with ICU collation in some cases wrongly return 0 rows

From: "Daniel Verite" <daniel(at)manitou-mail(dot)org>
To: "Jehan-Guillaume de Rorthais" <jgdr(at)dalibo(dot)com>
Cc: "Peter Eisentraut" <peter(dot)eisentraut(at)2ndquadrant(dot)com>,"Thomas Munro" <thomas(dot)munro(at)enterprisedb(dot)com>,"Peter Geoghegan" <pg(at)bowt(dot)ie>,"Роман Литовченко" <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: 2020-09-03 09:29:15
Message-ID: c00a63d3-f9c3-4222-a659-637232523b30@manitou-mail.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Jehan-Guillaume de Rorthais wrote:

> I really have no strong feeling right now about the best solution to adopt.
> However, I feel the least to do would be document it somewhere with a lot of
> strong emphasis.

Right now https://www.postgresql.org/docs/devel/collation.html
includes this example:

<quote>
CREATE COLLATION digitslast (provider = icu, locale = 'en-u-kr-latn-digit');
CREATE COLLATION digitslast (provider = icu, locale =
'en(at)colReorder=latn-digit');

Sort digits after Latin letters. (The default is digits before letters.)
</quote>

Now that we know that this collation is problematic, we could remove
this example, even if we don't want to go as far as documenting
ICU bugs. In fact bug reports used the same name "digitslast", so
I wonder if people tried this straight from our doc.

Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: https://www.manitou-mail.org
Twitter: @DanielVerite

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexander Korotkov 2020-09-03 17:32:59 Re: BUG #16606: V 4.25: unable to drop database
Previous Message Dave Page 2020-09-03 09:28:28 Re: Download page of Postgres not working