Re: Add standard collation UNICODE - Mailing list pgsql-hackers

From Joe Conway
Subject Re: Add standard collation UNICODE
Date
Msg-id 0d582110-50e6-3805-7e36-c7ee83ca4eba@joeconway.com
Whole thread Raw
In response to Re: Add standard collation UNICODE  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: Add standard collation UNICODE
List 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




pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: PGdoc: add missing ID attribute to create_subscription.sgml
Next
From: Tom Lane
Date:
Subject: Re: "variable not found in subplan target list"