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-09-01T23:01:22Z
Lists: pgsql-bugs
On Tue, Aug 18, 2020 at 9:02 AM Jehan-Guillaume de Rorthais <jgdr@dalibo.com> wrote: > I might be missing something, but according to my tests back in June, the bug > exists in both ucol_strcollUTF8()/ucol_strcoll() and is still affecting the very > last version of ICU (67.1). > > That's why my patch replaces both functions altogether using ucol_strcollIter > as replacement. I see. I misunderstood. > > This related ICU bug describes an issue affecting only versions 53/54: > > > > https://unicode-org.atlassian.net/browse/ICU-11388 > > This bug is related to ICU4J, not ICU4C. AS far as I understand, this was > related to a bad variable type when porting the code to java. Do I miss > something? That was based on a comment from TracBot on the bug tracker page you linked to. Clearly it's totally unrelated, though. I jumped the gun. -- 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