From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(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:38:17 |
Message-ID: | dbda1a9137aeab0f441104f212696b1c2d50d5f1.camel@j-davis.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
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?
> Arguably, if we are going to nudge toward ICU, maybe we should nudge
> toward UTF-8 as well.
The OSes are already doing a pretty good job of that. Regardless, we
need to remove the dependence on LC_CTYPE and LC_COLLATE when the
provider is ICU first (we're close to that point but not quite there).
Regards,
Jeff Davis
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2023-03-10 14:48:07 | Re: pgsql: Use ICU by default at initdb time. |
Previous Message | Peter Eisentraut | 2023-03-10 13:29:14 | pgsql: Fix tests for non-ICU build |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2023-03-10 14:48:07 | Re: pgsql: Use ICU by default at initdb time. |
Previous Message | Tom Lane | 2023-03-10 14:32:56 | Re: [PATCH] Add pretty-printed XML output option |