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

From Wolfgang Walther
Subject Re: PRI?64 vs Visual Studio (2022)
Date
Msg-id 2a2310f6-f836-467b-9f40-99cbb1dabd52@technowledgy.de
Whole thread Raw
In response to Re: PRI?64 vs Visual Studio (2022)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane:
> Thomas Munro <thomas.munro@gmail.com> writes:
>> On Tue, Dec 16, 2025 at 8:29 AM Peter Eisentraut <peter@eisentraut.org> wrote:
>>> I think that means that that gettext implementation is not currently
>>> supportable.  So either we revert our PRI* use except those two
>>> (unlikely), or those buildfarm members should disable NLS.
> 
>> Yeah.  My goal in mentioning the problem back when it was just a
>> problem in theory (we had no test, the Alpine packages disable nls
>> (perhaps it used to be *more* broken, if they did that before we used
>> PRI?)) was to try to see if someone closer to these musl distros
>> wanted to have a crack at fixing it, since it looks pretty close to
>> being usable.  But now that it's a problem in practice, it's hard to
>> disagree with Peter's take.  It could be reenabled any time it works
>> enough to pass the test.
> 
> Fair enough.  I've revised the test mechanism per discussion with
> Bryan Green, in hopes of being able to test on more BF animals than
> we could yesterday.  But I won't put in an expected-file for this
> Alpine misbehavior.

Both alpine animals now have NLS disabled.

Best,

Wolfgang



pgsql-hackers by date:

Previous
From: Melanie Plageman
Date:
Subject: Re: Checkpointer write combining
Next
From: "Matheus Alcantara"
Date:
Subject: Re: Some optimizations for COALESCE expressions during constant folding