Re: PRI?64 vs Visual Studio (2022)

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, walther(at)technowledgy(dot)de, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: PRI?64 vs Visual Studio (2022)
Date: 2025-12-15 19:43:40
Message-ID: CA+hUKG+pELXCHkAKAkbF-b5ot=imuoCCoYqhVSX4=pN_VtA3EA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Dec 16, 2025 at 8:29 AM Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
> On 15.12.25 08:01, Tom Lane wrote:
> > So their gettext handles PRIu64 and PRIu32 and nothing else.
> >
> > What to do now? I could revert 8c498479d and followups, but
> > I sure don't want to. A stopgap measure to make the farm look
> > green would be to add a variant expected-file that accepts
> > this output, but yech. Thoughts?
>
> 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2025-12-15 19:52:29 Re: Visibility bug in tuple lock
Previous Message Jeff Davis 2025-12-15 19:34:01 Re: Remaining dependency on setlocale()