Re: failover logical replication slots - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: failover logical replication slots
Date
Msg-id CAA4eK1Kv5UsiLn4bASoavjw1tRkEN1xiwA1koUaxpkujMckr1w@mail.gmail.com
Whole thread Raw
In response to Re: failover logical replication slots  (Fabrice Chapuis <fabrice636861@gmail.com>)
List pgsql-hackers
On Mon, Jul 14, 2025 at 9:10 PM Fabrice Chapuis <fabrice636861@gmail.com> wrote:
>
> Thanks for this feedback,
> I'll remove the check on the sync_replication_slots parameter.
> I think it is interesting as you suggest to start with the idea of the pg_alter_replication_slot API, I will make a
newproposal by opening a new thread, hoping to be supported in my approach. Is there already an initiative about the
pg_drop_all_slotsAPI? 
>

No, to my knowledge, there is no other initiative for the
pg_drop_all_slots() API. I think we first got the use case where users
can drop all slots on new standby after failover to avoid excessive
resource usage.

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Bertrand Drouvot
Date:
Subject: Re: Improve LWLock tranche name visibility across backends
Next
From: shveta malik
Date:
Subject: Re: Logical replication launcher did not automatically restart when got SIGKILL