Re: Add 64-bit XIDs into PostgreSQL 15
Julien Rouhaud <rjuju123@gmail.com>
From: Julien Rouhaud <rjuju123@gmail.com>
To: Pavel Borisov <pashkin.elfe@gmail.com>
Cc: "Finnerty, Jim" <jfinnert@amazon.com>, Simon Riggs <simon.riggs@enterprisedb.com>, Maxim Orlov <orlovmg@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2022-01-15T02:31:23Z
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
- v6-0001-Add-64-bit-GUCs-for-xids.patch (text/plain)
Hi, On Fri, Jan 14, 2022 at 11:38:46PM +0400, Pavel Borisov wrote: > > PFA patch with README for 64xid proposal. It is 0003 patch of the same v6, > that was proposed earlier [1]. > As always, I very much appreciate your ideas on this readme patch, on > overall 64xid patch [1], and on the roadmap on its improvement quoted above. Thanks for adding this documentation! Unfortunately, the cfbot can't apply a patchset split in multiple emails, so for now you only get coverage for this new readme file, as this is what's being tested on the CI: https://github.com/postgresql-cfbot/postgresql/commit/f8f12ce29344bc7c72665c334b5eb40cee22becd Could you send the full patchset each time you make a modification? For now I'm simply attaching 0001, 0002 and 0003 to make sure that the cfbot will pick all current patches on its next run.