Postgres Pro
Downloads
Home   >   mailing lists

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 CAJpy0uA7zD9r_OnXMvhkPwerpbiQFk01ubKKWN6T_H2HpByN7w@mail.gmail.com
Whole thread Raw
In response to Re: Track in pg_replication_slots the reason why slots conflict?  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Track in pg_replication_slots the reason why slots conflict?
List pgsql-hackers
Tree view 
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

pgsql-hackers by date:

Previous
From: vignesh C
Date:
Subject: Re: Commitfest manager January 2024
Next
From: Shubham Khanna
Date:
Subject: Re: Commitfest manager January 2024