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: wenhui qiu <qiuwenhuifx@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Evgeny <evorop@gmail.com>
Date: 2025-05-23T14:31:01Z
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 →
  1. Add SLRU tests for 64-bit page case

  2. Make use FullTransactionId in 2PC filenames

  3. Use larger segment file names for pg_notify

  4. Index SLRUs by 64-bit integers rather than by 32-bit integers

Attachments

Here is a new rebase @ 70a13c528b6e382a381f that includes solutions for the
previously mentioned issues as well as
a few more fixes and tweaks.

I decided to eliminate the TOAST flag for the function's parameters and
instead check pg_special for it.

As a result of 15a79c73111f0c9 and a0ed19e0a9efe9, we also have to utilise
the PRI* format string. At the moment, I'm
not sure how to integrate this into the existing patch set. I simply added
it on top of the existing ones. The only possibility
appears to be to return to the previous version in which the primary patch
of XIDs and the patch changing the message
format to 64 bits were combined.

-- 
Best regards,
Maxim Orlov.