Re: Track in pg_replication_slots the reason why slots conflict? - Mailing list pgsql-hackers

From shveta malik
Subject Re: Track in pg_replication_slots the reason why slots conflict?
Date
Msg-id CAJpy0uDL+ONASqrwbzWtZUgjb=U-jyRuEdwtkwNZf6a+bU7Kjg@mail.gmail.com
Whole thread Raw
In response to Re: Track in pg_replication_slots the reason why slots conflict?  (shveta malik <shveta.malik@gmail.com>)
Responses Re: Track in pg_replication_slots the reason why slots conflict?
List pgsql-hackers
On Mon, Jan 1, 2024 at 9:14 AM shveta malik <shveta.malik@gmail.com> wrote:
>
> On Fri, Dec 29, 2023 at 3:35 PM Michael Paquier <michael@paquier.xyz> wrote:
> >
> > On Fri, Dec 29, 2023 at 09:20:52AM +0530, Amit Kapila wrote:
> > > Does anyone have a preference for a column name? The options on the
> > > table are conflict_cause, conflicting_cause, conflict_reason. Any
> > > others? I was checking docs for similar usage and found
> > > "pg_event_trigger_table_rewrite_reason" function, so based on that we
> > > can even go with conflict_reason.
> >
> > "conflict_reason" sounds like the natural choice here.
>
> Do we have more comments on the patch apart from column_name?
>
> thanks
> Shveta

PFA v3 after changing column name to 'conflict_reason'

thanks
Shveta

Attachment

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Autonomous transactions 2023, WIP
Next
From: Bharath Rupireddy
Date:
Subject: Re: Remove unneeded PGDATABASE setting from TAP tests