From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@gmail.com>
cc: Peter Eisentraut <peter@eisentraut.org>,
        Kyotaro Horiguchi <horikyota.ntt@gmail.com>, walther@technowledgy.de,
        pgsql-hackers@lists.postgresql.org
Subject: Re: PRI?64 vs Visual Studio (2022)
In-reply-to: 
 <CA+hUKG+pELXCHkAKAkbF-b5ot=imuoCCoYqhVSX4=pN_VtA3EA@mail.gmail.com>
References: <20250331.152829.1921392690375275165.horikyota.ntt@gmail.com>
 <001bdc3b-ef94-4f24-b017-ac8ff0a2ea55@eisentraut.org>
 <CA+hUKGJnmzTqiODmTjf-23yZ=E3HXqFTtKoyp3TF-MpB93hTMQ@mail.gmail.com>
 <1372793.1763519315@sss.pgh.pa.us>
 <CA+hUKGLzXzQcbjEHW08Z6g=mzBkpLtzSJ7Bt2S2XmxP1bwpq8A@mail.gmail.com>
 <1377512.1763522154@sss.pgh.pa.us>
 <e7b902aa-98ac-4d35-bae3-d7d282a938c2@eisentraut.org>
 <1462038.1763567038@sss.pgh.pa.us>
 <CA+hUKG+nMv9bmOcARaDFC6rG=SGWC=TwWSRLrxi29oGeRNKemg@mail.gmail.com>
 <1881391.1765782112@sss.pgh.pa.us>
 <ef44619f-a25b-41e5-be87-d3971ff8c1d3@eisentraut.org>
 <CA+hUKG+pELXCHkAKAkbF-b5ot=imuoCCoYqhVSX4=pN_VtA3EA@mail.gmail.com>
Comments: In-reply-to Thomas Munro <thomas.munro@gmail.com>
	message dated "Tue, 16 Dec 2025 08:43:40 +1300"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <2257060.1765829966.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 15 Dec 2025 15:19:26 -0500
Message-ID: <2257061.1765829966@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2257061.1765829966%40sss.pgh.pa.us>
Precedence: bulk

Thomas Munro <thomas.munro@gmail.com> writes:
> On Tue, Dec 16, 2025 at 8:29=E2=80=AFAM Peter Eisentraut <peter@eisentra=
ut.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