Re: Add standard collation UNICODE
Jeff Davis <pgsql@j-davis.com>
From: Jeff Davis <pgsql@j-davis.com>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2023-03-23T20:16:35Z
Lists: pgsql-hackers
On Thu, 2023-03-09 at 11:23 -0800, Jeff Davis wrote: > Looks good to me. 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. I don't have a strong opinion here, but I thought I'd raise the issue. By my count, >50% of locales are actually just the root locale. I'm not sure if that should matter or not -- we don't want to weigh some locales over others -- but I found it interesting. Regards, Jeff Davis
Commits
-
initdb: Set collversion for standard collation UNICODE
- e32701b8d285 16.0 landed
-
Add standard collation UNICODE
- 0d21d4b9bc1f 16.0 landed