Re: Proposal: Conflict log history table for Logical Replication

Dilip Kumar <dilipbalaut@gmail.com>

From: Dilip Kumar <dilipbalaut@gmail.com>

To: Nisha Moond <nisha.moond412@gmail.com>

Cc: Peter Smith <smithpb2250@gmail.com>, vignesh C <vignesh21@gmail.com>, Amit Kapila <amit.kapila16@gmail.com>, shveta malik <shveta.malik@gmail.com>, Masahiko Sawada <sawada.mshk@gmail.com>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2026-04-16T15:54:06Z

Lists: pgsql-hackers

Attachments

v26-0003-Doccumentation-patch.patch (application/x-patch) patch v26-0003
v26-0001-Add-configurable-conflict-log-table-for-Logical.patch (application/x-patch) patch v26-0001
v26-0002-Implement-the-conflict-insertion-infrastructure-.patch (application/x-patch) patch v26-0002

On Fri, Apr 10, 2026 at 4:54 PM Nisha Moond <nisha.moond412@gmail.com> wrote:
>
> On Tue, Jan 27, 2026 at 9:24 AM Dilip Kumar <dilipbalaut@gmail.com> wrote:
> >
> > Also fixed all pending doc comments.
> >
>
> Hi Dilip,
> I’m planning to review/test the feature patches, but they don’t apply
> cleanly on the latest HEAD. Could you please rebase them?
>
 Thanks Nisha. Here is the rebased version


--
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