Re: Synchronizing slots from primary to standby - Mailing list pgsql-hackers

From Ashutosh Sharma
Subject Re: Synchronizing slots from primary to standby
Date
Msg-id CAE9k0PnGmQ97ikLy2oBDoom72FsV_x+H9JuptJ4ysx=CFM-+kQ@mail.gmail.com
Whole thread Raw
In response to Re: Synchronizing slots from primary to standby  (Andres Freund <andres@anarazel.de>)
Responses Re: Synchronizing slots from primary to standby
List pgsql-hackers
Hi Andres,

Are you talking about this scenario - what if the logical replication
slot on the publisher is dropped, but is being referenced by the
standby where the slot is synchronized? Should the redo function for
the drop replication slot have the capability to drop it on standby
and its subscribers (if any) as well?

--
With Regards,
Ashutosh Sharma.

On Sun, Feb 6, 2022 at 1:29 AM Andres Freund <andres@anarazel.de> wrote:
>
> Hi,
>
> On 2022-01-03 14:46:52 +0100, Peter Eisentraut wrote:
> > From ec00dc6ab8bafefc00e9b1c78ac9348b643b8a87 Mon Sep 17 00:00:00 2001
> > From: Peter Eisentraut <peter@eisentraut.org>
> > Date: Mon, 3 Jan 2022 14:43:36 +0100
> > Subject: [PATCH v3] Synchronize logical replication slots from primary to
> >  standby
>
> I've just skimmed the patch and the related threads. As far as I can tell this
> cannot be safely used without the conflict handling in [1], is that correct?
>
>
> Greetings,
>
> Andres Freund
>
> [1] https://postgr.es/m/CA%2BTgmoZd-JqNL1-R3RJ0jQRD%2B-dc94X0nPJgh%2BdwdDF0rFuE3g%40mail.gmail.com
>
>



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Use JOIN USING aliases in ruleutils.c
Next
From: Dilip Kumar
Date:
Subject: Re: Error "initial slot snapshot too large" in create replication slot