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 af9b96bd-0f9a-4e24-b98b-25d830999b06@technowledgy.de
Whole thread
In response to Re: PRI?64 vs Visual Studio (2022)  (Wolfgang Walther <walther@technowledgy.de>)
List pgsql-hackers
Wolfgang Walther:
> 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.

The update for gettext-tiny has made it into the latest Alpine release 
and with that the tests pass. I just enabled NLS for both Alpine animals 
again.

Best,

Wolfgang



pgsql-hackers by date:

Previous
From: Japin Li
Date:
Subject: Re: [PATCH] vacuumdb: Add --exclude-database option
Next
From: Ayush Tiwari
Date:
Subject: Re: PG19 FK fast path: OOB write and missed FK checks during batched