Re: Add 64-bit XIDs into PostgreSQL 15

Maxim Orlov <orlovmg@gmail.com>

From: Maxim Orlov <orlovmg@gmail.com>

To: Yura Sokolov <y.sokolov@postgrespro.ru>

Cc: Evgeny Voropaev <evgeny.voropaev@tantorlabs.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Andrey Borodin <x4mmm@yandex-team.ru>

Date: 2025-07-15T06:23:37Z

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

v65.zip (application/zip)

Rebase @ f5a987c0e5f6bbf0
Main conflicts were:
62a17a9283 Integrate FullTransactionIds deeper into two-phase code
2633dae2e4 Standardize LSN formatting by zero padding

Also, no setting XLOG_HEAP_INIT_PAGE on empty page as discussed above added.

On Mon, 7 Jul 2025 at 12:49, Yura Sokolov <y.sokolov@postgrespro.ru> wrote:
> Wow, it is really great bug.
It's funny that no one has actually encountered this problem in all these
years. It must
be a very rare mix of circumstances, I think.

Thank you very much, everyone, for participating!

-- 
Best regards,
Maxim Orlov.