Re: BUG #15285: Query used index over field with ICU collation in some cases wrongly return 0 rows
Peter Geoghegan <pg@bowt.ie>
From: Peter Geoghegan <pg@bowt.ie>
To: Jehan-Guillaume de Rorthais <jgdr@dalibo.com>
Cc: Thomas Munro <thomas.munro@gmail.com>, Роман Литовченко <roman.lytovchenko@gmail.com>, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2020-08-12T04:14:03Z
Lists: pgsql-bugs
On Fri, Jun 12, 2020 at 3:43 PM Jehan-Guillaume de Rorthais <jgdr@dalibo.com> wrote: > Please, find in attachment the second version of the patch, with a > regression test. Is it possible to fix this by making the existing HAVE_UCOL_STRCOLLUTF8 test more conservative about ICU version? IOW, by making it only use ucol_strcollUTF8() on versions that are known to not be affected by this bug? This related ICU bug describes an issue affecting only versions 53/54: https://unicode-org.atlassian.net/browse/ICU-11388 Why not just broaden the existing HAVE_UCOL_STRCOLLUTF8 workaround to recognize that the related functionality is broken on my versions of ICU than initially suspected? -- Peter Geoghegan
Commits
-
doc: Remove buggy ICU collation from documentation
- ddbb18743fd1 10.15 landed
- d0b585e86185 11.10 landed
- 697c8e620443 12.5 landed
- 9f358c5ef313 13.0 landed
- 4fff515e9eff 14.0 landed