Re: POC: make mxidoff 64 bits - Mailing list pgsql-hackers

From wenhui qiu
Subject Re: POC: make mxidoff 64 bits
Date
Msg-id CAGjGUA+uxpbkRaxkZmcSNiGXJ_G3Zj4-gzaiy=94DH7rvE8tig@mail.gmail.com
Whole thread Raw
In response to Re: POC: make mxidoff 64 bits  (Maxim Orlov <orlovmg@gmail.com>)
List pgsql-hackers
Hi Maxim 
     Thank you for your feedback.I remember this path the primary challenges are in the upgrade section, where we're still debating how to address a few edge cases. Right now, this thread is missing input from core code contributors.


Thanks

On Fri, Sep 19, 2025 at 12:37 AM Maxim Orlov <orlovmg@gmail.com> wrote:

On Tue, 16 Sept 2025 at 15:12, wenhui qiu <qiuwenhuifx@gmail.com> wrote:

Agree +1 , but I have a question: I remember the XID64 patch got split into a few threads. How are these threads related? The original one was seen as too big a change, so it was broken up after people raised concerns.  
Yeah, you're absolutely correct. This thread is a part of the overall
work on the transition to XID64 in Postgres. As far as I remember, no
one explicitly raised concerns, but it's clear to me that it won't be
committed as one big patch set.

Here is a WIP patch @ 8191e0c16a for the discussed above issue.
I also had to merge several patches from the previous set, since the
consensus is to use the PRI* format for outputting 64-bit values, and a
separate patch that only changed the format with cast and %llu lost
it's meaning.

If this option suits everyone, the next step is to add a part related
to the pg_upgrade.
 
--
Best regards,
Maxim Orlov.

pgsql-hackers by date:

Previous
From: Álvaro Herrera
Date:
Subject: Re: Having postgresql.org link to cgit instead of gitweb
Next
From: shveta malik
Date:
Subject: Re: Clear logical slot's 'synced' flag on promotion of standby