Re: Proposal: Conflict log history table for Logical Replication - Mailing list pgsql-hackers

From shveta malik
Subject Re: Proposal: Conflict log history table for Logical Replication
Date
Msg-id CAJpy0uCJsx4wKuG0iOLxJuGJ-RQRrumvgC0rQ6=4-t6krXMSEg@mail.gmail.com
Whole thread
In response to Re: Proposal: Conflict log history table for Logical Replication  (Dilip Kumar <dilipbalaut@gmail.com>)
List pgsql-hackers
On Fri, Apr 24, 2026 at 3:48 PM Dilip Kumar <dilipbalaut@gmail.com> wrote:
>
> 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.
>

Okay, thanks! Will review.

thanks
Shveta



pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: Proposal: Conflict log history table for Logical Replication
Next
From: Fujii Masao
Date:
Subject: Re: Exit walsender before confirming remote flush in logical replication