Re: Use CASEFOLD() internally rather than LOWER() - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Use CASEFOLD() internally rather than LOWER()
Date
Msg-id 449d14b3cb80e259bbd9d8728ea204b15b6a025a.camel@j-davis.com
Whole thread Raw
In response to Re: Use CASEFOLD() internally rather than LOWER()  (Mark Dilger <mark.dilger@enterprisedb.com>)
List pgsql-hackers
On Sat, 2026-03-21 at 20:14 -0700, Mark Dilger wrote:
> After v2-0001, ILIKE uses str_casefold() for matching, but pg_trgm
> still
> uses str_tolower() for trigram extraction (trgm_op.c:352 and :948).
> With builtin collations, these produce different results.

Interesting, thank you. As stated in the original message, I was unsure
about changing pg_trgm without adjusting the regex logic, also:

https://www.postgresql.org/message-id/64d7949bad90545f981ac7513fb0b4954daca2c9.camel@j-davis.com

do you have a suggestion about an easy way to do that, or should we
revisit in the next cycle?

Regards,
    Jeff Davis




pgsql-hackers by date:

Previous
From: Zsolt Parragi
Date:
Subject: Re: Stack-based tracking of per-node WAL/buffer usage
Next
From: Jeff Davis
Date:
Subject: Re: NLS: use gettext() to translate system error messages