Postgres Pro
Downloads
Home   >   mailing lists

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

From Peter Eisentraut
Subject Re: BUG #15285: Query used index over field with ICU collation in some cases wrongly return 0 rows
Date
Msg-id 4ea84116-4380-b12f-dcdf-7f2977ab2859@2ndquadrant.com
Whole thread Raw
In response to Re: BUG #15285: Query used index over field with ICU collation insome cases wrongly return 0 rows  (Jehan-Guillaume de Rorthais <jgdr@dalibo.com>)
Responses Re: BUG #15285: Query used index over field with ICU collation in some cases wrongly return 0 rows  (Jehan-Guillaume de Rorthais <jgdr@dalibo.com>)
List pgsql-bugs
Tree view 
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

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #16605: PostgreSQL recovery startup process waiting and blocking to application queries
Next
From: Jehan-Guillaume de Rorthais
Date:
Subject: Re: BUG #15285: Query used index over field with ICU collation in some cases wrongly return 0 rows