| From: | shveta malik <shveta(dot)malik(at)gmail(dot)com> |
|---|---|
| To: | Fabrice Chapuis <fabrice636861(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, shveta malik <shveta(dot)malik(at)gmail(dot)com> |
| Subject: | Re: Issue with logical replication slot during switchover |
| Date: | 2025-08-14 06:07:03 |
| Message-ID: | CAJpy0uCT9eodCyQT7n=QujOg+xJOc3swLRx4Pw3S7reR7pr6cQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 13, 2025 at 9:29 PM Fabrice Chapuis <fabrice636861(at)gmail(dot)com> wrote:
>
> Thanks for sharing this. In fact, I agree, introducing an allow_overwrite slot property makes seems cleaner than a GUC for this specific use case.
>
> a) At first, an extension of pg_create_logical_replication_slot() could be proposed
> b) pg_alter_logical_replication_slot(): that could be is a neat approach, a generic API for modifying other slot properties seems like a forward-looking design choice. However I don't know if slot properties could be modified easily because when slot is active, a process is holding them in memory.
Right, it can not be.This API can be used when the slot is not
acquired by any other process. We may have use-cases for that as well
similar to one we have for this switchover case.
thanks
Shveta
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kirill Reshke | 2025-08-14 06:35:15 | Re: VM corruption on standby |
| Previous Message | Michael Paquier | 2025-08-14 05:49:06 | Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) |