Re: Add 64-bit XIDs into PostgreSQL 15
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Heikki Linnakangas <hlinnaka@iki.fi>, Maxim Orlov <orlovmg@gmail.com>, Yura Sokolov <y.sokolov@postgrespro.ru>,
Evgeny Voropaev <evgeny.voropaev@tantorlabs.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
Andrey Borodin <x4mmm@yandex-team.ru>
Date: 2026-02-12T18:52:30Z
Lists: pgsql-hackers
Hi, On 2026-02-09 08:40:48 -0500, Robert Haas wrote: > On Sun, Feb 8, 2026 at 12:21 PM Andres Freund <andres@anarazel.de> wrote: > > On the topic of pd_prune_xid - I've been wondering if, instead of the double > > xmax approach, the high bits of the 64bit xid could be stored in pd_prune_xid, > > signified by a flag on the page indicating so. > > We potentially have both XIDs and MXIDs to worry about, though. I don't think mxids are a problem for the case of needing to update a page that doesn't have space for the new pd_special region (with both xid and mxid epoch), because you can always can just replace mxids with the underlying xids when you're in that situation, they have to be old enough for that to be possible. Or you could even create new multixacts, but I don't think that should ever be needed. Greetings, Andres Freund
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add SLRU tests for 64-bit page case
- a60b8a58f435 17.0 landed
-
Make use FullTransactionId in 2PC filenames
- 5a1dfde8334b 17.0 landed
-
Use larger segment file names for pg_notify
- 2cdf131c46e6 17.0 landed
-
Index SLRUs by 64-bit integers rather than by 32-bit integers
- 4ed8f0913bfd 17.0 landed