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

From Nikhil Shetty
Subject Re: Proposal: Conflict log history table for Logical Replication
Date
Msg-id CAFpL5Vx-HAhMhJ-m9b71APrZpwsDwzZzMFWr3figau2mef-__g@mail.gmail.com
Whole thread
In response to Re: Proposal: Conflict log history table for Logical Replication  (shveta malik <shveta.malik@gmail.com>)
List 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

pgsql-hackers by date:

Previous
From: Rafia Sabih
Date:
Subject: Re: postgres_fdw: Emit message when batch_size is reduced
Next
From: Zakariyah Ali
Date:
Subject: Re: [PATCH] Fix missing-field-initializers and sign comparison warnings