Re: Add 64-bit XIDs into PostgreSQL 15

Maxim Orlov <orlovmg@gmail.com>

From: Maxim Orlov <orlovmg@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Zhang Mingli <zmlpostgres@gmail.com>, Justin Pryzby <pryzby@telsasoft.com>, Dilip Kumar <dilipbalaut@gmail.com>, Pavel Borisov <pashkin.elfe@gmail.com>, Aleksander Alekseev <aleksander@timescale.com>, pgsql-hackers@lists.postgresql.org, Stephen Frost <sfrost@snowman.net>, Alexander Korotkov <aekorotkov@gmail.com>, Andres Freund <andres@anarazel.de>, Ilya Anfimov <ilan@tzirechnoy.com>
Date: 2022-10-21T16:09:15Z
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

>
> This patch set needs a rebase, as far as I can see.
>

Done! Thanks! Here is the rebased version.

This version has bug fix for multixact replication. Previous versions of
the patch set does not write pd_multi_base in WAL. Thus, this field was set
to 0 upon WAL reply on replica.
This caused replica to panic. Fix this by adding pd_multi_base of a page
into WAL. Appropriate tap test is added.

Also, add refactoring and improvements in heapam.c in order to reduce diff
and make it more "tidy".

Reviews and opinions are very welcome!

-- 
Best regards,
Maxim Orlov.