Re: Patch for migration of the pg_commit_ts directory

ls7777 <ls7777@yandex.ru>

From: ls7777 <ls7777@yandex.ru>

To: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>, Masahiko Sawada <sawada.mshk@gmail.com>

Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, "orlovmg@gmail.com" <orlovmg@gmail.com>, "amit.kapila16@gmail.com" <amit.kapila16@gmail.com>

Date: 2026-03-21T08:59:11Z

Lists: pgsql-hackers

Attachments

(unnamed) (text/html)
v12-Migration-of-the-pg_commit_ts-directory.patch (text/x-diff) patch v12

  
    Hi,
  
  
     
  
  
    
      The patch has been significantly updated.
    
    
      1. Added the --pg-commit-ts command line key for pg_upgrade.
    
    
      Migration of the pg_commit_ts directory will be performed only if the user explicitly wishes.
    
    
      2. The roident values are being transferred from pg_replication_origin to a new cluster to resolve conflict messages {UPDATE|DELETE}_ORIGIN_DIFFERS.
    
    
       
    
    
      During testing, it turned out that the replication sources created by the pg_replication_origin_create('no_link_sub_4') functions are not migrated to the new cluster. This is probably a bug.
    
    
       
    
    
      The principle of operation: A query to the old cluster generates SQL commands for roident adjustments, which are then executed in the new cluster.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →