Re: pgsql: Use ICU by default at initdb time.

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgsql: Use ICU by default at initdb time.
Date: 2023-03-10 14:48:07
Message-ID: ebe9a63f-d4c6-7553-1e58-7dd80a11c1c1@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 10.03.23 15:38, Jeff Davis wrote:
> On Fri, 2023-03-10 at 10:59 +0100, Peter Eisentraut wrote:
>> I think originally the locale forced the encoding.  With ICU, we have
>> a
>> choice.  We could either stick to the encoding suggested by the OS,
>> or
>> pick our own.
>
> We still need LC_COLLATE and LC_CTYPE to match the database encoding
> though. If we get those from the environment (which are connected to an
> encoding), then I think we need to get the encoding from the
> environment, too, right?

Yes, of course. So we can't really do what I was thinking of.

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Jeff Davis 2023-03-10 15:48:13 Re: pgsql: Use ICU by default at initdb time.
Previous Message Jeff Davis 2023-03-10 14:38:17 Re: pgsql: Use ICU by default at initdb time.

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-03-10 15:09:26 Re: Date-Time dangling unit fix
Previous Message Jeff Davis 2023-03-10 14:38:17 Re: pgsql: Use ICU by default at initdb time.