I wrote:
> PG Bug reporting form <noreply@postgresql.org> writes:
>> I downloaded the latest installer for windows and tried to install a local
>> database server with locale Norwegian Bokmål. Looks like this bug is back in
>> version 17? Or maybe it's windows 11 that is causing it?
> Sigh, did they rename it again?
Oh, never mind that. I'd forgotten about this recent change:
<para>
Disallow locale names containing non-ASCII characters (Thomas Munro)
</para>
<para>
This is only an issue on Windows, as such locale names are not used
elsewhere. They are problematic because it's quite unclear what
encoding such names are represented in (since the locale itself
defines the encoding to use). In
recent <productname>PostgreSQL</productname> releases, an abort in
the Windows runtime library could occur because of confusion about
that.
</para>
<para>
Anyone who encounters the new error message should either create a
new duplicated locale with an ASCII-only name using Windows Locale
Builder, or consider using BCP 47-compliant locale names
like <literal>tr-TR</literal>.
</para>
So your fix is to specify the locale explicitly to initdb,
along the lines of "--locale=no-NO" (I'm guessing about the
Norwegian locale to use, but it's probably close to that).
Was the error you got not sufficiently clear about this?
regards, tom lane
