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

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Роман Литовченко <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-01 23:01:22
Message-ID: CAH2-WzkdHtt=AzVAQHPLX=5QQjETZodwfBy_9wKBhtOBjwp0dQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Aug 18, 2020 at 9:02 AM Jehan-Guillaume de Rorthais
<jgdr(at)dalibo(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2020-09-01 23:03:08 Re: BUG #16594: DROP INDEX CONCURRENTLY fails on partitioned table with a non helpful error message.
Previous Message Dave Cramer 2020-09-01 22:35:46 Re: BUG #16557: getProcedureColumns() function returns columns, when there is no existing Stored Procedure in the DB