| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | 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-02 12:06:18 |
| Message-ID: | 4ea84116-4380-b12f-dcdf-7f2977ab2859@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2020-06-10 00:29, Jehan-Guillaume de Rorthais wrote:
> In the meantime, I've been working on various workarounds. The only one I found
> is to use "fr-u-kr-latn-digit-kn" instead of "fr-u-kr-latn-digit".
> Unfortunately, the two collations are not equivalent, but I believe it might be
> useful in many case.
What precisely is broken in the ICU library? All the examples so far
refer to kr-latn-digit. Are all reorderings broken, or something
specifically related to latn and/or digit? Are any collation
customizations other than reorderings affected?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jehan-Guillaume de Rorthais | 2020-09-02 12:55:50 | Re: BUG #15285: Query used index over field with ICU collation in some cases wrongly return 0 rows |
| Previous Message | PG Bug reporting form | 2020-09-02 10:58:49 | BUG #16605: PostgreSQL recovery startup process waiting and blocking to application queries |