Re: BUG #19602: Vuln46: citext split_part silently returns NULL for a zero field position instead of raising core sp

Hi Jaehyuck,

You were right on both points; v3, attached, has both changes.

On Thu, Nov 12, 2026 at 2:29 PM Jaehyuck Sa
<jaehyuck(dot)sa(dot)dev(at)gmail(dot)com> wrote:
> With -2, it
> would return 'c' only when the match is case-insensitive, so I think
> it would catch a missing 'i'. (The same goes for the 'aΔbδc' line in
> citext_utf8.sql.)

Both lines now use -2. With 'gi' changed to 'g', the two -1 lines
passed and the two -2 lines fail; the tests still catch an unescaped
pattern or replacement string as before.

> I think only the
> wording needs to change

Done as you suggested. Of the eight locales I tried on Linux,
U+01C5 ~* U+01C5 is true only with the plain C locale (libc and
builtin); it is false with builtin C.UTF-8 and PG_UNICODE_FAST,
libc en_US.UTF-8 and C.UTF-8, and ICU. I could not try macOS.

Regards,
Manu