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 CAA4eK1J1PpF4vA9tdCPUka7M+W3FH=X3k6eSL_qFq+wVcK65Cg@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, Apr 27, 2026 at 9:51 PM Dilip Kumar <dilipbalaut@gmail.com> wrote:
>
> On Mon, Apr 27, 2026 at 3:08 PM shveta malik <shveta.malik@gmail.com> wrote:
> >
>
> > 3)
> > Also I would like to know which one is better here:
> >
> > \dRs+ giving 'Conflict log table' in tabular format (current way)
> >
> > Or giving it as 'Conflict log table' at the end, like:
> >
> > Conflict Log Table:
> >     "pg_conflict.pg_conflict_16395"
> >
> > I’m slightly inclined toward option 2, similar to how \dRp shows
> > “Tables” and “Except tables” at the end; it catches the eye faster.
> > But I don't have a strong opinion here. I'd be interested to hear what
> > others think.
>
> I am not completely convinced, but I don't have a strong opinion
> against it, so as you said, let's hear from others as well.
>

Is there a need to even show the CLT name? We create origin also as
part of subscription but don't display its name in this command.

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: Fix race condition in pg_get_publication_tables with concurrent DROP TABLE
Next
From: Haibo Yan
Date:
Subject: Re: Introduce new multi insert Table AM and improve performance of various SQL commands with it for Heap AM