Feedback-ID: ie0a040ee:Fastmail
Message-ID: <aadafbe2-b731-4009-bb9a-b2e55cf32c83@eisentraut.org>
Date: Thu, 4 Apr 2024 14:05:27 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Built-in CTYPE provider
To: Jeff Davis <pgsql@j-davis.com>, Daniel Verite <daniel@manitou-mail.org>
Cc: Robert Haas <robertmhaas@gmail.com>,
 Jeremy Schneider <schneider@ardentperf.com>, pgsql-hackers@postgresql.org
References: <6f3e94c0-f174-4380-9b69-072f8a838881@manitou-mail.org>
 <2692039df6b0cac20c5e488fa0209e8958c5fedb.camel@j-davis.com>
 <27bb0e52-801d-4f73-a0a4-02cfdd4a9ada@eisentraut.org>
 <4a69d067374d2f6bfb66f5bfb2ab9a020493d49f.camel@j-davis.com>
 <3bc653b5d562ae9e2838b11cb696816c328a489a.camel@j-davis.com>
 <163f4e2190cdf67f67016044e503c5004547e5a9.camel@j-davis.com>
 <6bdb98e68b2b05aa71f7f934e227738eac84ecee.camel@j-davis.com>
 <19b34a70-f5cf-4faf-88dc-917db44ed48d@eisentraut.org>
 <846a7e1fa2024918b58ff7583523a2f3de9a11b4.camel@j-davis.com>
 <3117d30aa911b408b90420f4f280fa0c3b5851be.camel@j-davis.com>
 <4135cf11-206d-40ed-96c0-9363c1232379@eisentraut.org>
 <7451f81ba0cb512222ab759de8ca1cffe44e9acb.camel@j-davis.com>
 <1f309153-8198-4efa-86dd-8c304ec0040c@eisentraut.org>
 <a21b515000f121244db2a5570d4292d19df23379.camel@j-davis.com>
 <a8804ef9-fda6-4660-9f98-ecd1315f958c@eisentraut.org>
 <480c02813ee26e83e305d015be6a63059bb3ddd8.camel@j-davis.com>
Content-Language: en-US
From: Peter Eisentraut <peter@eisentraut.org>
In-Reply-To: <480c02813ee26e83e305d015be6a63059bb3ddd8.camel@j-davis.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/aadafbe2-b731-4009-bb9a-b2e55cf32c83%40eisentraut.org>
Precedence: bulk

On 01.04.24 21:52, Jeff Davis wrote:
> On Tue, 2024-03-26 at 08:04 +0100, Peter Eisentraut wrote:
>> The patch set v27 is ok with me, modulo (a) discussion about initcap
>> semantics, and (b) what collation to assign to ucs_basic, which can
>> be
>> revisited later.
> 
> Attached v28.
> 
> The remaining patches are for full case mapping and PG_UNICODE_FAST.
> 
> I am fine waiting until July to get these remaining patches committed.
> That would give us time to sort out details like:
> 
> * Get consensus that it's OK to change UCS_BASIC.
> * Figure out if we need a pg-specific locale and whether
> PG_UNICODE_FAST is the right name.
> * Make sure that full case mapping interacts with regexes in a sane way
> (probably it needs to just fall back to simple case mapping, but
> perhaps that's worth a discussion).
> * Implement case folding.
> * Implement a more unicode-friendly TITLECASE() function, which could
> offer a number of options that don't fit well with INITCAP().
> * Figure out if UPPER()/LOWER() should also have some of those options.
> 
> Thoughts?

Yeah, I think it's good to give some more time to work out these things. 
  The features committed for PG17 so far are solid, so it's a good point 
to pause.