Postgres Pro
Downloads
Home   >   mailing lists

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

From Amit Kapila
Subject Re: Track in pg_replication_slots the reason why slots conflict?
Date
Msg-id CAA4eK1L8VnvO6nndGPv3dN9wyX+2bx8f5tWZxa0jYUce7Eku2Q@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
Tree view 
On Thu, Dec 28, 2023 at 2:58 PM shveta malik <shveta.malik@gmail.com> wrote:
>
> PFA the v2-patch with all your comments addressed.
>

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.

--
With Regards,
Amit Kapila.

pgsql-hackers by date:

Previous
From: Andrei Lepikhov
Date:
Subject: Re: POC: GROUP BY optimization
Next
From: Amit Kapila
Date:
Subject: Re: Synchronizing slots from primary to standby