Horton
Menu

Re: Proposal: Conflict log history table for Logical Replication

Nikhil Shetty <nikhil.dba04@gmail.com>

View thread
From: Nikhil Shetty <nikhil.dba04@gmail.com>
To: shveta malik <shveta.malik@gmail.com>
Cc: Dilip Kumar <dilipbalaut@gmail.com>, Shlok Kyal <shlok.kyal.oss@gmail.com>, vignesh C <vignesh21@gmail.com>, Peter Smith <smithpb2250@gmail.com>, Nisha Moond <nisha.moond412@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-06-19T13:26:22Z
Lists: pgsql-hackers 
I see, thanks for the clarification.

On Fri, 19 Jun 2026 at 18:07, shveta malik <shveta.malik@gmail.com> wrote:

> On Fri, Jun 19, 2026 at 5:57 PM Nikhil Shetty <nikhil.dba04@gmail.com>
> wrote:
> >
> > Hi Dilip,
> >
> > I was just testing this patch.I was thinking if we can have another
> column which stores the timestamp when the conflict happened. This will be
> useful for debugging purposes.
> >
>
> We discussed this earlier and plan to consider potential approaches
> once base-patch is committed. See the discussiosn around [1] and [2].
>
> [1]:
> https://www.postgresql.org/message-id/CAJpy0uC54cxVYNRTfFXY_986-54HTVDNE1srn_Z9pGGDYhDjcw%40mail.gmail.com
> [2]:
> https://www.postgresql.org/message-id/CAA4eK1J0PJHR8XMx3zRyBkhVHkKAcMfqXT20t0E8qievY81LOw%40mail.gmail.com
>
> thanks
> Shveta
>

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