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: Amit Kapila <amit.kapila16@gmail.com>
Cc: Nisha Moond <nisha.moond412@gmail.com>, shveta malik <shveta.malik@gmail.com>, Peter Smith <smithpb2250@gmail.com>, vignesh C <vignesh21@gmail.com>, Masahiko Sawada <sawada.mshk@gmail.com>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-07-06T10:18:53Z
Lists: 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

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