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

From Dilip Kumar
Subject Re: Proposal: Conflict log history table for Logical Replication
Date
Msg-id CAFiTN-vuhMhMwCdArfMx_t+HH-3d5=OBLMaD12m=Ft_Nr5id=A@mail.gmail.com
Whole thread
In response to Re: Proposal: Conflict log history table for Logical Replication  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Proposal: Conflict log history table for Logical Replication
List pgsql-hackers
On Mon, Jul 6, 2026 at 3:27 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Mon, Jul 6, 2026 at 1:14 PM Dilip Kumar <dilipbalaut@gmail.com> wrote:
> >
> > On Fri, Jul 3, 2026 at 5:25 PM Nisha Moond <nisha.moond412@gmail.com> wrote:
> > >
> > > For the pushed patch (commit a5918fd), it seems we missed updating the
> > > pg_subscription catalog documentation for the two newly added columns:
> > >
> > > subconflictlogrelid | oid  |           | not null |
> > > subconflictlogdest  | text | C         | not null |
> > >
> > > Attached is a small patch for the same.
> >
> > Yeah that make sense, also added a extra change suggested by Peter for
> > <firstterm> markup.
> >
>
> Did you consider changing the code comments as suggested by me in
> email [1] to address Peter's complaint on repetitiveness of code
> comments?
>
> [1] - https://www.postgresql.org/message-id/CAA4eK1LH9N80WbFe88Lp0fFrXosVpYnh8iqtrh9kpfJR5N%3Dpyg%40mail.gmail.com
>

Not yet, I thought we hadn't reached a conclusion on this part.


--
Regards,
Dilip Kumar
Google



pgsql-hackers by date:

Previous
From: Dean Rasheed
Date:
Subject: Re: Global temporary tables
Next
From: Peter Eisentraut
Date:
Subject: Re: SECURITY LABEL ON PROPERTY GRAPH: supported?