| From: | ls7777 <ls7777(at)yandex(dot)ru> |
|---|---|
| To: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "orlovmg(at)gmail(dot)com" <orlovmg(at)gmail(dot)com>, "amit(dot)kapila16(at)gmail(dot)com" <amit(dot)kapila16(at)gmail(dot)com> |
| Subject: | Re: Patch for migration of the pg_commit_ts directory |
| Date: | 2026-03-21 08:59:11 |
| Message-ID: | 6741774083455@mail.yandex.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
| Attachment | Content-Type | Size |
|---|---|---|
| unknown_filename | text/html | 856 bytes |
| v12-Migration-of-the-pg_commit_ts-directory.patch | text/x-diff | 19.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2026-03-21 09:57:40 | Re: [Proposal] Adding Log File Capability to pg_createsubscriber |
| Previous Message | jian he | 2026-03-21 08:16:07 | Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions |