From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Add standard collation UNICODE |
Date: | 2023-03-28 12:46:17 |
Message-ID: | 0d582110-50e6-3805-7e36-c7ee83ca4eba@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2023-03-28 12:56:41 | Re: "variable not found in subplan target list" |
Previous Message | Amit Kapila | 2023-03-28 12:23:09 | Re: PGdoc: add missing ID attribute to create_subscription.sgml |