Horton

Re: Add 64-bit XIDs into PostgreSQL 15

Evgeny Voropaev <evgeny.voropaev@tantorlabs.com>

View thread
From: Evgeny Voropaev <evgeny.voropaev@tantorlabs.com>
To: wenhui qiu <qiuwenhuifx@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2024-12-17T07:28:07Z
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

> Hi Evgeny
>      xid64 path split several threads ,The current one should be 
> this:(https://www.postgresql.org/message-id/flat/CACG=ezaWg7_nt-8ey4aKv2w9LcuLthHknwCawmBgEeTnJrJTcw@mail.gmail.com) 
> ,We can do some tests on path so that  can merge earlier
> Thanks
Hello Wenhui!

Thank you for pointing out the specific topic developing the Multixact 
ID Offset MXIDOFF64 solution. I agree to the fullest extent with 
community's decision to split the xid64 into smaller parts and 
subsequently merge them into the master. In the meantime, abandoning the 
full version of the original patch and developing only its fragments, we 
are causing the target solution to become staled. That is why I have 
tried to put the whole solution together. The xid64 patch (v56-v58) 
includes the MXIDOFF patch as a distinct files. The first four 
patch-files of the xid64 are exactly the 9th version of the MXIDOFF64. 
If new versions of the xid64 patch update the parts relevant to 
MXIDOFF64, we will add them into MXIDOFF64 thread as a next version. I 
also hope you and the community will support attempts to retain the 
whole xid64 solution in the consistent state because only the consistent 
state allows us to continually test and fix the xid64 solution.

Best regards,
Evgeny Voropaev,
Tantor Labs LLC.