Re: [PG19] ILIKE index scan misses rows with a libc UTF-8 collation on macOS

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
To: shihao zhong <zhong950419(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Jeff Davis <pgsql(at)j-davis(dot)com>, Noah Misch <noah(at)leadboat(dot)com>
Subject: Re: [PG19] ILIKE index scan misses rows with a libc UTF-8 collation on macOS
Date: 2026-10-20 03:16:49
Message-ID: FE015EF5-0C4E-4AC2-9D67-08EAAA8F010C@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Oct 20, 2026, at 10:20, shihao zhong <zhong950419(at)gmail(dot)com> wrote:
>
> Where the C
> library is consistent it changes nothing.

Not really. On unaffected platforms, an unmatched char originally goes through 2 checks, now 4 checks, and the latter two are redundant, which adds overhead on unaffected platforms.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2026-10-20 03:25:32 Re: [PATCH] initdb: map Windows' new Canadian time zone names
Previous Message Denis Smirnov 2026-10-20 03:14:56 Re: Fold NOT IN / <> ALL expressions containing NULL to FALSE