From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com> |
Cc: | Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Windows default locale vs initdb |
Date: | 2022-07-29 03:33:50 |
Message-ID: | CA+hUKG+zcZw7zmPw4nAQCv1b-78UBSxKifWjOYtCGu9KLKG7Xw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jul 22, 2022 at 11:59 PM Juan José Santamaría Flecha
<juanjo(dot)santamaria(at)gmail(dot)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 done through 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?
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2022-07-29 04:20:37 | Re: generic plans and "initial" pruning |
Previous Message | Amit Kapila | 2022-07-29 03:29:07 | Re: Functions 'is_publishable_class' and 'is_publishable_relation' should stay together. |