Re: Proposal: Conflict log history table for Logical Replication

Dilip Kumar <dilipbalaut@gmail.com>

From: Dilip Kumar <dilipbalaut@gmail.com>

To: vignesh C <vignesh21@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-13T10:16:40Z

Lists: pgsql-hackers

Attachments

v50-0001-Add-configurable-conflict-log-table-for-Logical-.patch (application/octet-stream) patch v50-0001
v50-0002-Report-error-for-ddls-on-conflict-log-tables.patch (application/octet-stream) patch v50-0002
v50-0003-Implement-the-conflict-insertion-infrastructure-.patch (application/octet-stream) patch v50-0003
v50-0005-Add-conflict-log-table-information-to-describe-s.patch (application/octet-stream) patch v50-0005
v50-0004-Preserve-conflict-log-destination-and-subscripti.patch (application/octet-stream) patch v50-0004
v50-0006-Documentation-patch.patch (application/octet-stream) patch v50-0006

On Thu, Jun 11, 2026 at 5:53 PM vignesh C <vignesh21@gmail.com> wrote:
>
> 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.

Please find attached the latest patch. I have reordered the series,
moving 0006 to 0002, and updated the lock restrictions. We now allow
ACCESS SHARE mode exclusively to ensure pg_dump can acquire its
necessary locks, while blocking higher-level locks to prevent
interference with insertions into the conflict log tables.

-- 
Regards,
Dilip Kumar
Google

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