Re: Track in pg_replication_slots the reason why slots conflict?

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Amit Kapila <amit.kapila16@gmail.com>

Cc: shveta malik <shveta.malik@gmail.com>, Isaac Morland <isaac.morland@gmail.com>, Andres Freund <andres@anarazel.de>, Postgres hackers <pgsql-hackers@lists.postgresql.org>, Bertrand Drouvot <bertranddrouvot.pg@gmail.com>

Date: 2023-12-29T10:05:07Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Track conflict_reason in pg_replication_slots.
- 007693f2a3ac 17.0 landed

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