I'm using the "postgresql-9.2.0-1-windows.exe" installer, from
Enterprise DB, on a Windows Vista 32-bit computer.
The issue was noticed with the GUI installer, where I chose the local
option "English, New Zealand" from a drop-down menu, but the resulting
database cluster has "English_United States
Furthermore, to compare with initdb.exe from 9.1 on the same computer,
here are the key : value pairs from the --locale="key" and locale
used.
>"C:\Program Files\PostgreSQL\9.1\bin\initdb.exe" --version
initdb (PostgreSQL) 9.1.4
C : C
English : English
French : French
nonsense : English_United Ki
Apologies for multiple email threads, as this message was sent before
my other email and before adding my account to this list. This bug
report is slightly misleading, as the --locale option is not ignored
by initdb.exe, but is misinterpreted in certain cases.
See email thread: "initdb.exe changes
Testing on another Windows OS, here is a similar key : value exercise,
described previously. The system is Windows 7 64-bit, with a system
locale: "en-nz;English (New Zealand)" (from systeminfo.exe). The
version of initdb.exe is 9.2.0, and the full command-line is:
>"C:\Program Files\PostgreSQL\9.
I've found a general solution: with the locale string, replace the
first ", " (comma space) with "_".
Around line 33 of initcluster.vbs, add:
strLocale = Replace(strLocale,", ","_",1,1)
I think it is fine to show "English, New Zealand" in the drop-down
menu for the GUI installer, but initcluster
Apologies that this report is near trivial, and only concerns the
Windows installers by EnterpriseDB (I'm not sure where else to post
these).
With all of the current EnterpriseDB builds for Windows, several files
have inconsistent line endings, switching between so-called DOS
(CR+LF) and UNIX (LF)
