Re: Add 64-bit XIDs into PostgreSQL 15
Zhang Mingli <zmlpostgres@gmail.com>
From: Zhang Mingli <zmlpostgres@gmail.com>
To: Michael Paquier <michael@paquier.xyz>, Maxim Orlov
<orlovmg@gmail.com>
Cc: 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-22T03:21:55Z
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
- v48-0009-remove-some-outdate-codes-comments-about-xidWrap.patch (application/octet-stream) patch v48-0009
Hi, On Oct 22, 2022, 00:09 +0800, Maxim Orlov <orlovmg@gmail.com>, wrote: > > > > 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. Found some outdate code comments around several variables, such as xidWrapLimit/xidWarnLimit/xidStopLimt. These variables are not used any more. I attach an additional V48-0009 patch as they are just comments, apply it if you want to. Regards, Zhang Mingli