| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Fabrice Chapuis <fabrice636861(at)gmail(dot)com> |
| Cc: | "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: failover logical replication slots |
| Date: | 2025-07-15 10:31:05 |
| Message-ID: | CAA4eK1Kv5UsiLn4bASoavjw1tRkEN1xiwA1koUaxpkujMckr1w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jul 14, 2025 at 9:10 PM Fabrice Chapuis <fabrice636861(at)gmail(dot)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 new proposal by opening a new thread, hoping to be supported in my approach. Is there already an initiative about the pg_drop_all_slots API?
>
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shveta malik | 2025-07-15 10:34:26 | Re: Logical replication launcher did not automatically restart when got SIGKILL |
| Previous Message | Bertrand Drouvot | 2025-07-15 10:18:16 | Re: Improve LWLock tranche name visibility across backends |