Re: POC: make mxidoff 64 bits

From: Maxim Orlov <orlovmg(at)gmail(dot)com>
To: wenhui qiu <qiuwenhuifx(at)gmail(dot)com>
Cc: Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: POC: make mxidoff 64 bits
Date: 2025-09-18 16:37:11
Message-ID: CACG=ezaCKR+--O2TZrm3jYGgpDjdpLXdz3marG6t_=nzP5+Gog@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 16 Sept 2025 at 15:12, wenhui qiu <qiuwenhuifx(at)gmail(dot)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.

Attachment Content-Type Size
v18-wip-0001-Use-64-bit-multixact-offsets.patch application/octet-stream 31.7 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2025-09-18 16:48:27 Re: Invalid primary_slot_name triggers warnings in all processes on reload
Previous Message Robert Haas 2025-09-18 16:19:45 Re: PG 18 relnotes and RC1