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

From Michael Paquier
Subject Re: Track in pg_replication_slots the reason why slots conflict?
Date
Msg-id ZY6Z05oXknNlqGXH@paquier.xyz
Whole thread Raw
In response to Re: Track in pg_replication_slots the reason why slots conflict?  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Track in pg_replication_slots the reason why slots conflict?
List pgsql-hackers
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.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: "Andrey M. Borodin"
Date:
Subject: Re: libpq compression (part 3)
Next
From: Richard Guo
Date:
Subject: Re: Revise the Asserts added to bimapset manipulation functions