Re: Order changes in PG16 since ICU introduction
От | Joe Conway |
---|---|
Тема | Re: Order changes in PG16 since ICU introduction |
Дата | |
Msg-id | 6b3df50c-3195-4f40-e04f-c25f489383f7@joeconway.com обсуждение исходный текст |
Ответ на | Re: Order changes in PG16 since ICU introduction ("Daniel Verite" <daniel@manitou-mail.org>) |
Ответы |
Re: Order changes in PG16 since ICU introduction
|
Список | pgsql-hackers |
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
В списке pgsql-hackers по дате отправления: