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.96) (envelope-from ) id 1vVE65-00Gfm0-17 for pgsql-hackers@arkaria.postgresql.org; Mon, 15 Dec 2025 19:19:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vVE64-001wCE-10 for pgsql-hackers@arkaria.postgresql.org; Mon, 15 Dec 2025 19:19:05 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vVE64-001wC5-04 for pgsql-hackers@lists.postgresql.org; Mon, 15 Dec 2025 19:19:04 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vVE63-000puc-1l for pgsql-hackers@lists.postgresql.org; Mon, 15 Dec 2025 19:19:03 +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 5BFJJ1gY2128695; Mon, 15 Dec 2025 14:19:01 -0500 From: Tom Lane To: Bryan Green cc: pgsql-hackers@lists.postgresql.org Subject: Re: PRI?64 vs Visual Studio (2022) In-reply-to: References: <20250331.152829.1921392690375275165.horikyota.ntt@gmail.com> <001bdc3b-ef94-4f24-b017-ac8ff0a2ea55@eisentraut.org> <1372793.1763519315@sss.pgh.pa.us> <1377512.1763522154@sss.pgh.pa.us> <1462038.1763567038@sss.pgh.pa.us> <1881391.1765782112@sss.pgh.pa.us> <1991599.1765818338@sss.pgh.pa.us> <2117910.1765823286@sss.pgh.pa.us> Comments: In-reply-to Bryan Green message dated "Mon, 15 Dec 2025 13:06:09 -0600" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2128693.1765826341.1@sss.pgh.pa.us> Date: Mon, 15 Dec 2025 14:19:01 -0500 Message-ID: <2128694.1765826341@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Bryan Green writes: > On 12/15/2025 12:28 PM, Tom Lane wrote: >> ... It did work if I set lc_messages to 'C.utf8', which is a >> known name according to this box's "locale -a", but this doesn't give >> me a warm feeling about this approach being a lot more portable than >> what we have. Any ideas? > My answer did not feel like it was right, so I checked multiple versions > and realized there is a check. > ... > C.utf8 works because it is not "C" so is treated as a real locale. Ah-hah. I didn't think they hadn't optimized the case at all. Experimenting here, it looks like 'C.UTF-8' might be accepted everywhere. I even got it to pass on Solaris's not-GNU gettext, which I thought for sure would be the weak spot in the idea. I'll press forward with that. regards, tom lane