Re: Windows default locale vs initdb - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Windows default locale vs initdb
Date
Msg-id CA+hUKGKTYM3tYNr=zau1H73KpzDPuL_Ebs_cDgvvZE5xtjEH-g@mail.gmail.com
Whole thread Raw
In response to Re: Windows default locale vs initdb  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Windows default locale vs initdb
List pgsql-hackers
On Tue, Jul 23, 2024 at 1:44 AM Andrew Dunstan <andrew@dunslane.net> wrote:
> I have an environment I can use for testing. But what exactly am I
> testing? :-) Install a few "problem" language/region settings, switch
> the system and ensure initdb runs ok?

I just want to know about any weird unexpected consequences of using
BCP47 locale names, before we change the default in v18.  The only
concrete thing I found so far was that MinGW didn't like it, but I
provided a fix for that.  It'd still be possible to initialise a new
cluster with the old style names if you really want to, but you'd have
to pass it in explicitly; I was wondering if that could be necessary
in some pg_upgrade scenario but I guess not, it just clobbers
template0's pg_database row with values from the source database, and
recreates everything else so I think it should be fine (?).  I am a
little uneasy about the new names not having .encoding but there
doesn't seem to be an issue with that (such locales exist on Unix
too), and the OS still knows which encoding they use in that case.



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: pg_upgrade and logical replication
Next
From: Peter Smith
Date:
Subject: Re: Pgoutput not capturing the generated columns