Re: PostgreSQL Windows Installer defaults to "English_United States.1252" when choosing locale starting with "English"

Yes, you are correct. I got the same result. But it was correct when I
chose the BCP-47 name like en-uk. Probably something to do with how initdb
is handling the long names.

On Mon, Jul 7, 2025 at 5:50 PM Sandeep Thakkar <
sandeep.thakkar@enterprisedb.com> wrote:

> Hi,
>
> I'll have a look and revert.
>
> On Sun, Jul 6, 2025 at 5:09 PM Ben Caspi <benc@aidoc.com> wrote:
>
>> Hi,
>>
>> In the past we reached out to you about the PostgreSQL Windows
>> installer not having an option to modify the locale on installation,
>> resulting in failures during upgrades due to mismatched locale versions.
>>
>> As a result you released installer version 15.13, which included a more
>> inclusive locale flag which solves our problem.
>>
>> However, we recently noticed that when picking a locale starting with
>> "English", the value post installation will always be "English_United
>> States.1252".
>>
>> For example, we installed using locale "English, United Kingdom" and
>> expected the locale value post installation to be "English_United
>> Kingdom.1252". However, we saw it was installed with the "English_United
>> States.1252" locale instead.
>>
>> We then tested multiple different locales and found this issue repeats
>> only when choosing locales starting with "English".
>>
>> Is this the intended behavior? If not, we would appreciate a fix to this
>> issue as it's blocking us from upgrading our machines holding older
>> PostgreSQL versions.
>>
>> Thank you!
>>
>> --
>>
>> [image: photo]
>>
>> Ben Caspi
>> DevOps Engineer
>>
>> www.aidoc.com  |  benc@aidoc.com
>>
>> [image: linkedin] <https://www.linkedin.com/company/aidoc/>
>>
>> [image: twitter] <https://twitter.com/aidocmed>
>>
>> [image: App Banner Image] <https://www.aidoc.com/book-a-demo/>
>>
>>
>
>
> --
> Sandeep Thakkar
>
>
>

-- 
Sandeep Thakkar