Re: Add standard collation UNICODE
Joe Conway <mail@joeconway.com>
From: Joe Conway <mail@joeconway.com>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
Jeff Davis <pgsql@j-davis.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2023-03-28T12:46:17Z
Lists: pgsql-hackers
On 3/28/23 06:07, Peter Eisentraut wrote: > On 23.03.23 21:16, Jeff Davis wrote: >> Another thought: for ICU, do we want the default collation to be >> UNICODE (root collation)? What we have now gets the default from the >> environment, which is consistent with the libc provider. >> >> But now that we have the UNICODE collation, it makes me wonder if we >> should just default to that. The server's environment doesn't >> necessarily say much about the locale of the data stored in it or the >> locale of the applications accessing it. > > As long as we still have to initialize the libc locale fields to some > language, I think it would be less confusing to keep the ICU locale on > the same language. I definitely agree with that. > If we ever manage to get rid of that, then I would also support making > the ICU locale the root collation by default. +1 -- Joe Conway PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com
Commits
-
initdb: Set collversion for standard collation UNICODE
- e32701b8d285 16.0 landed
-
Add standard collation UNICODE
- 0d21d4b9bc1f 16.0 landed