Re: PRI?64 vs Visual Studio (2022)

From: Wolfgang Walther <walther(at)technowledgy(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: PRI?64 vs Visual Studio (2022)
Date: 2025-12-15 21:59:37
Message-ID: 2a2310f6-f836-467b-9f40-99cbb1dabd52@technowledgy.de
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane:
> Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
>> On Tue, Dec 16, 2025 at 8:29 AM Peter Eisentraut <peter(at)eisentraut(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Matheus Alcantara 2025-12-15 22:09:06 Re: Some optimizations for COALESCE expressions during constant folding
Previous Message Melanie Plageman 2025-12-15 21:50:31 Re: Checkpointer write combining