Re: PRI?64 vs Visual Studio (2022) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: PRI?64 vs Visual Studio (2022)
Date
Msg-id 2128694.1765826341@sss.pgh.pa.us
Whole thread Raw
In response to Re: PRI?64 vs Visual Studio (2022)  (Bryan Green <dbryan.green@gmail.com>)
Responses Re: PRI?64 vs Visual Studio (2022)
List pgsql-hackers
Bryan Green <dbryan.green@gmail.com> 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



pgsql-hackers by date:

Previous
From: Bryan Green
Date:
Subject: Re: PRI?64 vs Visual Studio (2022)
Next
From: Peter Eisentraut
Date:
Subject: Re: [PATCH] Fix severe performance regression with gettext 0.20+ on Windows