Re: Add 64-bit XIDs into PostgreSQL 15

Evgeny Voropaev <evorop.wiki@gmail.com>

From: Evgeny Voropaev <evorop.wiki@gmail.com>

To: Maxim Orlov <orlovmg@gmail.com>

Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>

Date: 2025-06-11T06:00: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 →

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

 > What exactly would break if we did perform `heap_page_prune_execute`
 > with NO fragmentation repair during `heap_page_prepare_for_xid`?

Correction into the last question:

What exactly would break if we did invoke `heap_page_prune_execute` with 
`repairFragmentation=true` during performing of `heap_page_prepare_for_xid`?