Re: Proposal: Conflict log history table for Logical Replication
vignesh C <vignesh21@gmail.com>
From: vignesh C <vignesh21@gmail.com>
To: Dilip Kumar <dilipbalaut@gmail.com>
Cc: shveta malik <shveta.malik@gmail.com>,
Amit Kapila <amit.kapila16@gmail.com>, Nisha Moond <nisha.moond412@gmail.com>, Peter Smith <smithpb2250@gmail.com>, Masahiko Sawada <sawada.mshk@gmail.com>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-06-11T12:22:50Z
Lists: pgsql-hackers
Attachments
- v49-0003-Preserve-conflict-log-destination-and-subscripti.patch (application/octet-stream) patch v49-0003
- v49-0001-Add-configurable-conflict-log-table-for-Logical-.patch (application/octet-stream) patch v49-0001
- v49-0005-Documentation-patch.patch (application/octet-stream) patch v49-0005
- v49-0004-Add-conflict-log-table-information-to-describe.patch (application/octet-stream) patch v49-0004
- v49-0002-Implement-the-conflict-insertion-infrastructure-.patch (application/octet-stream) patch v49-0002
- v49-0006-Report-error-for-ddls-on-conflict-log-tables.patch (application/octet-stream) patch v49-0006
On Thu, 11 Jun 2026 at 10:44, Dilip Kumar <dilipbalaut@gmail.com> wrote: > > Please find the rebased patch > 1. It includes the new 0005 patch for reporting errors for DDLs on clt. > > Open comments: > 1. Recent comments from Nisha and Shveta after v47 are still open > 2. Vignesh's patch for "describe related" changes needs a rebase. Can > you do that, Vignesh? Meanwhile, I will close all the open comments > and try to share a new version by EOD today. Here is the rebased version of the patch attached. Regards, Vignesh
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Allow logical replication conflicts to be logged to a table.
- a5918fddf10d master landed
-
Avoid orphaned objects dependencies
- 2fbb21170e90 19 (unreleased) cited