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 09:59:12
Message-ID: dab5ce1a-0f1d-38cd-1cb4-f2b0b2d229e0@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 10.03.23 03:26, Jeff Davis wrote:
> That's because ICU always uses UTF-8 by default. ICU works just fine
> with many other encodings; is there a reason it doesn't take it from
> the environment just like for provider=libc?

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.

Arguably, if we are going to nudge toward ICU, maybe we should nudge
toward UTF-8 as well.

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2023-03-10 10:18:58 pgsql: Add a test for UCS_BASIC collation
Previous Message Peter Eisentraut 2023-03-10 09:54:14 Re: pgsql: Allow tailoring of ICU locales with custom rules

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2023-03-10 10:03:04 Re: logical decoding and replication of sequences, take 2
Previous Message Önder Kalacı 2023-03-10 09:54:48 Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher