Re: Issue with logical replication slot during switchover
| От | Alexander Kukushkin |
|---|---|
| Тема | Re: Issue with logical replication slot during switchover |
| Дата | |
| Msg-id | CAFh8B=nZYwLB78LZO+VEE3MoYKL5GXYsim_hjy1wP7k6numZ+A@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Issue with logical replication slot during switchover (Fabrice Chapuis <fabrice636861@gmail.com>) |
| Ответы |
Re: Issue with logical replication slot during switchover
|
| Список | pgsql-hackers |
Hi Fabrice,
On Fri, 31 Oct 2025 at 17:45, Fabrice Chapuis <fabrice636861@gmail.com> wrote:
Thanks for your large analyze and explanation Alexander. If we go in the direction you propose and leave the option to use a suplementary flag allow_overwrite, may I propose you some modifications in the patch v0 you have attached:Why modifying this function?drop_local_obsolete_slots(List *remote_slot_list)
Think about the following case:
1. We have node1 (primary) and node2 (standby), with slot foo(failover=true)
2. We stop node1 for maintenance and promote node2
3. DROP replication slot on node2
4. Start node1
In this scenario the logical slot "foo" will be left unattended and it needs to be dropped, because it doesn't exist on the primary.
As I said earlier, IMO it is only the "failover" flag that effectively indicates the purpose of the slot. The sync flag is purely informative.
Regards,
--
Alexander Kukushkin
В списке pgsql-hackers по дате отправления: