| 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-08-12 04:14:03 |
| Message-ID: | CAH2-Wz=dN99ptML=DYnNt+byRBA8cnbHiHh=Ei7a0NPRQ89CYw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Jun 12, 2020 at 3:43 PM Jehan-Guillaume de Rorthais
<jgdr(at)dalibo(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2020-08-12 05:19:12 | Re: posgres 12 bug (partitioned table) |
| Previous Message | Tom Lane | 2020-08-12 04:08:10 | Re: posgres 12 bug (partitioned table) |