Re: Add 64-bit XIDs into PostgreSQL 15
Maxim Orlov <orlovmg@gmail.com>
From: Maxim Orlov <orlovmg@gmail.com>
To: Evgeny Voropaev <evgeny.voropaev@tantorlabs.com>
Cc: y.sokolov@postgrespro.ru, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2025-07-02T15:38:07Z
Lists: pgsql-hackers
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
Attachments
- v64.zip (application/zip)
On Tue, 1 Jul 2025 at 14:08, Evgeny Voropaev <evgeny.voropaev@tantorlabs.com> wrote: > > And that difference in the HEAP_XMAX_COMMITED is the inconsistency, even > when it is in garbage on a page. And, probably, it is not the only > example of the problem. > I can't imagine that this action would cause any real issues. If you know of any real problems, please tell me. Although I'm not particularly against the idea of zeroing tuples, I don't see much point in it, to be honest. But to ensure everyone's peace of mind, I've made yet another commit that accomplishes this. -- Best regards, Maxim Orlov.