|From:||Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>|
|To:||Peter Geoghegan <pg(at)bowt(dot)ie>|
|Cc:||Роман Литовченко <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|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Fri, Jul 20, 2018 at 11:26 AM, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> On Thu, Jul 19, 2018 at 9:44 AM, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>> It appears that the main support function 1 routine disagrees with the
>> CREATE INDEX sort order, which is wrong. I'll try to isolate the
>> problem a bit further.
> As far as I can tell, this is an ICU bug. ucol_strcollUTF8() is buggy
> with this digitslast collation, which ucol_nextSortKeyPart() fails to
> be bug-compatible with. Other similar customized collations (e.g.
> 'en-u-kf-upper') work fine. (Ugh, that's familiar in an unpleasant
> I'm using libicu60. What version are you using, Roman?
> I tried to find something that matches this on the ICU bug tracker.
> This might be a match: https://ssl.icu-project.org/trac/ticket/12518
FWIW I see the same result with icu 61.1 and 62.1_1 from FreeBSD ports.
|Next Message||Tom Lane||2018-07-21 05:44:26||Re: BUG #15287: postgres_fdw: the "WHERE date_trunc('day', dt) = 'YYYY-MM-DD' does not push to remote.|
|Previous Message||Marko Tiikkaja||2018-07-20 21:56:13||Re: BUG #15182: Canceling authentication due to timeout aka Denial of Service Attack|