Re: Issue with logical replication slot during switchover

From: Fabrice Chapuis <fabrice636861(at)gmail(dot)com>
To: shveta malik <shveta(dot)malik(at)gmail(dot)com>
Cc: Alexander Kukushkin <cyberdemn(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com>
Subject: Re: Issue with logical replication slot during switchover
Date: 2025-10-31 08:15:57
Message-ID: CAA5-nLAUgxXCKKH+Gv2sFgXXV4TAcb+qpwMpGZ9babEOGe5Bfw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,
I indeed proposed a solution at the top of this thread to modify only the
value of the synced attribute, but the discussion was redirected to adding
an extra parameter to the function *pg_create_logical_replication_slot() *to
overwrite a failover slot

Regards,

Fabrice

On Fri, Oct 31, 2025 at 5:32 AM shveta malik <shveta(dot)malik(at)gmail(dot)com> wrote:

> On Tue, Oct 28, 2025 at 6:33 PM Alexander Kukushkin <cyberdemn(at)gmail(dot)com>
> wrote:
> >
> > Hi all,
> >
> > I don't think we really need to have allow_overwrite.
> > It is not possible to create logical slots on standby with
> failover=true, therefore we can safely rely on failover being true to
> understand that at some point this node was a primary and that this slot is
> supposed to be synced.
> > Please see the patch attached.
> >
>
> We had discussed this point in another thread, please see [1]. After
> discussion it was decided to not go this way.
>
> [1]:
> https://www.postgresql.org/message-id/OS0PR01MB57161FF469DE049765DD53A89475A%40OS0PR01MB5716.jpnprd01.prod.outlook.com
>
> thanks
> Shveta
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Shardul Borhade 2025-10-31 08:17:22 Question on pg_stat_io showing zero reads/writes for I/O workers
Previous Message wenhui qiu 2025-10-31 08:00:54 Re: Report oldest xmin source when autovacuum cannot remove tuples