Horton
Menu

Re: Proposal: Conflict log history table for Logical Replication

Dilip Kumar <dilipbalaut@gmail.com>

View thread
From: Dilip Kumar <dilipbalaut@gmail.com>
To: shveta malik <shveta.malik@gmail.com>
Cc: Nisha Moond <nisha.moond412@gmail.com>, Peter Smith <smithpb2250@gmail.com>, vignesh C <vignesh21@gmail.com>, Amit Kapila <amit.kapila16@gmail.com>, Masahiko Sawada <sawada.mshk@gmail.com>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-04-24T10:18:37Z
Lists: pgsql-hackers 
On Fri, Apr 24, 2026 at 11:42 AM shveta malik <shveta.malik@gmail.com> wrote:
>
> On Tue, Apr 21, 2026 at 3:21 PM Dilip Kumar <dilipbalaut@gmail.com> wrote:
> >
> > Thanks Nisha for the review. All your comments make sense so I have
> > fixed them in the latest patch.
> >
>
> Hi Dilip,
>
> Before we resume review, could you summarize any pending design points
> (if any) from our last discussion? Sorry, I have lost track, a summary
> will help.

Thanks Shveta, IIRC, there were no open design point, the last problem
were related to user should not be able to modify the internally
created conflict log table and for that we designed a pg_conflict
schema.  So maybe we can dig a bit deeper on this part related to
whether we are ensuring all right sort of permissions on this schema.

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

  1. Allow logical replication conflicts to be logged to a table.

  2. Avoid orphaned objects dependencies