Re: PRI?64 vs Visual Studio (2022) - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: PRI?64 vs Visual Studio (2022)
Date
Msg-id CA+hUKGJaX3AcuKSdEUOZiWc+mzL=+dvGnbMqCvWGY22y6oh9Nw@mail.gmail.com
Whole thread Raw
In response to Re: PRI?64 vs Visual Studio (2022)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PRI?64 vs Visual Studio (2022)
List pgsql-hackers
On Mon, Dec 15, 2025 at 8:01 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> So their gettext handles PRIu64 and PRIu32 and nothing else.

Hah, I had predicted that three would work.  Off by one.

> 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?

So close yet so far... I tried asking if it's easy to fix:

https://github.com/sabotage-linux/gettext-tiny/issues/76



pgsql-hackers by date:

Previous
From: Oleg Tkachenko
Date:
Subject: Re: [BUG] [PATCH] pg_basebackup produces wrong incremental files after relation truncation in segmented tables
Next
From: Amit Kapila
Date:
Subject: Re: Proposal: Conflict log history table for Logical Replication