Message-ID: <6b3df50c-3195-4f40-e04f-c25f489383f7@joeconway.com>
Date: Tue, 6 Jun 2023 14:11:18 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.11.0
Content-Language: en-US
To: Daniel Verite <daniel@manitou-mail.org>, Jeff Davis <pgsql@j-davis.com>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
 Andrew Gierth <andrew@tao11.riddles.org.uk>, Tom Lane <tgl@sss.pgh.pa.us>,
 pgsql-hackers@lists.postgresql.org
References: <45f0cd77-9c85-4c5e-9396-adbccdb635e2@manitou-mail.org>
From: Joe Conway <mail@joeconway.com>
Subject: Re: Order changes in PG16 since ICU introduction
In-Reply-To: <45f0cd77-9c85-4c5e-9396-adbccdb635e2@manitou-mail.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/6b3df50c-3195-4f40-e04f-c25f489383f7%40joeconway.com>
Precedence: bulk

On 6/6/23 09:09, Daniel Verite wrote:
> 	Jeff Davis wrote:
>> New patch series attached. I plan to commit 0001 and 0002 soon, unless
>> there are objections.
>> 
>> 0001 causes the "C" and "POSIX" locales to be treated with
>> memcmp/pg_ascii semantics in ICU, just like in libc. We also
>> considered a new "none" provider, but it's more invasive, and we can
>> always reconsider that in the v17 cycle.

> 0001 creates exceptions throughout the code so that when an ICU
> collation has a locale name "C" or "POSIX" then it does not behave
> like an ICU collation, even though pg_collation.collprovider='i'
> To me it's neither desirable nor necessary that a collation that
> has collprovider='i' is diverted to non-ICU semantics.

This discussion makes me wonder (though probably too late for the v16 
cycle) if we shouldn't treat "C" and "POSIX" locales to be a third 
provider, something like "internal".

-- 
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com