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

From Amit Kapila
Subject Re: Proposal: Conflict log history table for Logical Replication
Date
Msg-id CAA4eK1LrUSYKOHX+TtQT8kF5QqGh0HTBDtgFAfYxhRc4Qj_Uuw@mail.gmail.com
Whole thread
In response to Re: Proposal: Conflict log history table for Logical Replication  (Dilip Kumar <dilipbalaut@gmail.com>)
Responses Re: Proposal: Conflict log history table for Logical Replication
List pgsql-hackers
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

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Dean Rasheed
Date:
Subject: Re: Global temporary tables
Next
From: Dean Rasheed
Date:
Subject: Re: Global temporary tables