| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org>, Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com> |
| Cc: | 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 08:26:03 |
| Message-ID: | 0df88ec9-90c6-54cb-ca63-7aafa5903b0c@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2020-09-03 09:41, Daniel Verite wrote:
> Jehan-Guillaume de Rorthais wrote:
>
>> Maybe Daniel has some more experience feedback with other customizations
>
> No, I've just tried various other reorderings, and didn't find any other that
> seems to have the same bug as latn-digit.
> My tests consisted of indexing a large corpus of text and running the
> index through amcheck.
In this case I'm tempted to just leave it alone and write it off as a
bug in ICU. We could potentially inspect the collator object at CREATE
COLLATION time and issues warnings if we find something we know to be buggy.
I don't think we want to make our code uglier and slower for normal uses
to work around a bug in some niche feature in ICU.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2020-09-03 08:43:38 | BUG #16606: V 4.25: unable to drop database |
| Previous Message | Vibhor Mark Steele | 2020-09-03 07:48:17 | Download page of Postgres not working |