Patch for migration of the pg_commit_ts directory v2

From: ls7777 <ls7777(at)yandex(dot)ru>
To: "kuroda(dot)hayato(at)fujitsu(dot)com" <kuroda(dot)hayato(at)fujitsu(dot)com>, "amit(dot)kapila16(at)gmail(dot)com" <amit(dot)kapila16(at)gmail(dot)com>, "orlovmg(at)gmail(dot)com" <orlovmg(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Patch for migration of the pg_commit_ts directory v2
Date: 2025-10-04 16:08:06
Message-ID: 9971759592114@mail.yandex.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Hi

 


Thank you all for the helpful tips. Many thanks to Alex Orlov for the test. He works.


I made a second version of the patch and took into account all the comments.



Patch description: When checking a new cluster, the value of the track_commit_timestamp parameter is determined. 


If this parameter is set and the Latest checkpoint's oldestCommitTsXid and Latest checkpoint's newestCommitTsXid are set in the old cluster, then pg_comit_ts is copied.



The files were processed by pgindent.


 




 

 

Attachment Content-Type Size
unknown_filename text/html 633 bytes
v2-0001-Migration-of-the-pg_commit_ts-directory.patch text/x-diff 9.6 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-10-04 17:38:55 Re: We broke the defense against accessing other sessions' temp tables
Previous Message Amit Kapila 2025-10-04 15:54:32 Re: Logical Replication of sequences