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

From Thomas Munro
Subject Re: Windows default locale vs initdb
Date
Msg-id CA+hUKG+zcZw7zmPw4nAQCv1b-78UBSxKifWjOYtCGu9KLKG7Xw@mail.gmail.com
Whole thread Raw
In response to Re: Windows default locale vs initdb  (Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>)
Responses Re: Windows default locale vs initdb
List pgsql-hackers
On Fri, Jul 22, 2022 at 11:59 PM Juan José Santamaría Flecha
<juanjo.santamaria@gmail.com> wrote:
> TL;DR; What I want to show through this example is that Windows ACP is not modified by setlocale(), it can only be
donethrough the Windows registry and only in recent releases. 

Thanks, that was helpful, and so was that SO link.

So it sounds like I should forget about the v3-0002 patch, but the
v3-0001 and v3-0003 patches might have a future.  And it sounds like
we might need to investigate maybe defending ourselves against the ACP
being different than what we expect (ie not matching the database
encoding)?  Did I understand correctly that you're looking into that?



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Functions 'is_publishable_class' and 'is_publishable_relation' should stay together.
Next
From: Amit Langote
Date:
Subject: Re: generic plans and "initial" pruning