Re: Add CASEFOLD() function.
Peter Eisentraut <peter@eisentraut.org>
From: Peter Eisentraut <peter@eisentraut.org>
To: Thom Brown <thom@linux.com>, Jeff Davis <pgsql@j-davis.com>
Cc: Vik Fearing <vik@postgresfriends.org>, Joe Conway <mail@joeconway.com>,
Ian Lawrence Barwick <barwick@gmail.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2025-06-19T14:51:02Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix PDF doc build.
- d2ca16bb509c 18.0 landed
-
Add SQL function CASEFOLD().
- bfc5992069cf 18.0 landed
-
Add support for Unicode case folding.
- 4e7f62bc386a 18.0 landed
On 19.06.25 06:03, Thom Brown wrote:
> Late to the party, but is there an argument for porting this to the
> citext type? Or supplementing the extension with an additional type
> ("cftext"? *shrug*). It currently uses lower(), so our current
> recommendation for dealing with all unicode characters is to use
> nondeterministic collations.
What is the motivation for wanting a citext variant instead of using
nondeterministic collations?