On Thu, Jul 10, 2025 at 12:41 AM Sandeep Thakkar <sandeep.thakkar@enterprisedb.com> wrote: > 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.
What's the exact initdb command in this case? I'm a bit confused about ""English, United Kingdom" vs "English_United Kingdom.1252". I think maybe the Windows C library is doing this, because that first form isn't really a supported form, and it only manages to grok the first word with some best-match scheme? I don't have Windows but I just pushed a stupid test program to CI to test that theory:
Here is the initdb command: --- Executing: "C:\Program Files\PostgreSQL\17\bin\initdb.exe" --pgdata="C:\Program Files\PostgreSQL\17\data" --username="postgres" --encoding=UTF8 --pwfile="C:\Users\sandeep\AppData\Local\Temp\postgresql_installer_c27ed92f26\212da2e5.tmp" --auth=scram-sha-256 --locale="English, United Kingdom"
The files belonging to this database system will be owned by user "sandeep". This user must also own the server process.
The database cluster will be initialized with locale "English_United States.1252". The default text search configuration will be set to "english".