Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1tfiB2-004Vjz-Sq
	for pgsql-bugs@arkaria.postgresql.org; Wed, 05 Feb 2025 16:23:01 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1tfiB1-00FiIV-Kp
	for pgsql-bugs@arkaria.postgresql.org; Wed, 05 Feb 2025 16:22:59 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1tfiB1-00FiIM-CV
	for pgsql-bugs@lists.postgresql.org; Wed, 05 Feb 2025 16:22:59 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by magus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1tfiAv-003Wem-1w
	for pgsql-bugs@lists.postgresql.org;
	Wed, 05 Feb 2025 16:22:58 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 515GMprl816920;
	Wed, 5 Feb 2025 11:22:51 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: oystein.arneson@cloudberries.no
cc: pgsql-bugs@lists.postgresql.org
Subject: =?UTF-8?Q?Re:_BUG_#18795:_Norwegian_bokm=C3=A5l_crashes_again?=
In-reply-to: <816216.1738772073@sss.pgh.pa.us>
References: <18795-268389c4e50cbd4e@postgresql.org>
 <816216.1738772073@sss.pgh.pa.us>
Comments: In-reply-to Tom Lane <tgl@sss.pgh.pa.us>
	message dated "Wed, 05 Feb 2025 11:14:33 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <816918.1738772571.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 05 Feb 2025 11:22:51 -0500
Message-ID: <816919.1738772571@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/816919.1738772571%40sss.pgh.pa.us>
Precedence: bulk

I wrote:
> PG Bug reporting form <noreply@postgresql.org> writes:
>> I downloaded the latest installer for windows and tried to install a lo=
cal
>> database server with locale Norwegian Bokm=C3=A5l. 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=3Dno-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