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

From: Ben Caspi <benc(at)aidoc(dot)com>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: Liran Amrani <lirana(at)aidoc(dot)com>, Avi Uziel <avi(dot)uziel(at)aidoc(dot)com>, Shahar Amram <shahara(at)aidoc(dot)com>
Subject: PostgreSQL Windows Installer defaults to "English_United States.1252" when choosing locale starting with "English"
Date: 2025-07-06 11:06:05
Message-ID: CABv1Mx5XYcMO9g_B7eaPogibu13WVmzoUpZ6Bvb1yj9xBCEBNA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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(at)aidoc(dot)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/>

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2025-07-06 13:58:20 BUG #18979: pg_upgrade to PG17 fails if max_slot_wal_keep_size is not set to -1
Previous Message Tom Lane 2025-07-05 16:13:08 Re: Unexpected behavior when setting "idle_replication_slot_timeout"