Re: fixing tsearch locale support - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: fixing tsearch locale support
Date
Msg-id 2a134365-6b32-4a3b-aee4-10a48be0cd79@eisentraut.org
Whole thread Raw
In response to Re: fixing tsearch locale support  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-hackers
On 26.08.25 18:52, Heikki Linnakangas wrote:
>> So maybe the release notes should say
>> "now observes the locale provider configured for the database to
>> convert strings to lower case".
> 
> Is it only used for converting to lower case, or is there any other 
> operations that need to be mentioned? Converting to upper case too I 
> presume. (I haven't been following this thread)

It's actually only lower case.  (It should really be casefold, but that 
might be a separate project for another day.)  But after reading this a 
few times, just writing "for converting to lower case" led me to ask 
"but what about upper case", so I reworded it to "case conversion".

> We only support two collation providers, libc and ICU right? That makes 
> Peter's phrasing "In database clusters that use a locale provider other 
> than libc ..." an unnecessarily complicated way of saying ICU.

There is the "builtin" provider, and it is affected by this as well.

> It's pretty urgent to get the release notes in shape, people are testing 
> upgrades with the betas already...

I have committed this release note item with some adjustment now.




pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Assert single row returning SQL-standard functions
Next
From: Julien Tachoires
Date:
Subject: Re: Qual push down to table AM