Horton

Re: Proposal: Conflict log history table for Logical Replication

shveta malik <shveta.malik@gmail.com>

View thread
From: shveta malik <shveta.malik@gmail.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: vignesh C <vignesh21@gmail.com>, Dilip Kumar <dilipbalaut@gmail.com>, Nisha Moond <nisha.moond412@gmail.com>, Peter Smith <smithpb2250@gmail.com>, Masahiko Sawada <sawada.mshk@gmail.com>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, shveta malik <shvetamalik@gmail.com>
Date: 2026-05-12T09:26:25Z
Lists: pgsql-hackers 
On Tue, May 12, 2026 at 2:51 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Tue, May 12, 2026 at 12:00 PM shveta malik <shveta.malik@gmail.com> wrote:
> >
> > I had earlier suggested a timestamp column (pt 3 at [1]) to record
> > conflict-occurence time (mainly 'conflict_logged_at' column) in CLT
> > but the idea was kept on hold awaiting more feedback. Now we can
> > revisit this.
> >
> > I feel 'conflict_logged_at' could be more beneficial because, going
> > forward (based on feedback), we may range-partition this table on that
> > field which may form as basis of historical data purge. I also
> > suggested this in [2] (see 'That said, irrespective of what we
> > decide') . Such a field could be basis of purging mechanism.
> >
>
> Fair enough. We can extend the table with this field after more
> discussion, so it will be better to pick up this discussion once the
> base feature is committed.
>

Okay. Works for me.

thanks
Shveta