Re: PRI?64 vs Visual Studio (2022)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: 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>, 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 20:19:26
Message-ID: 2257061.1765829966@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2025-12-15 20:23:44 Re: Small patch to improve safety of utf8_to_unicode().
Previous Message Robert Haas 2025-12-15 20:13:31 Re: [BUG] [PATCH] pg_basebackup produces wrong incremental files after relation truncation in segmented tables