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

From Amit Kapila
Subject Re: Synchronizing slots from primary to standby
Date
Msg-id CAA4eK1J5D-Z7dFa89acf7O+Ca6Y9bygTpi52KAKVCg+PE+Zfog@mail.gmail.com
Whole thread Raw
In response to Re: Synchronizing slots from primary to standby  ("Drouvot, Bertrand" <bertranddrouvot.pg@gmail.com>)
Responses Re: Synchronizing slots from primary to standby
Re: Synchronizing slots from primary to standby
List pgsql-hackers
On Wed, Nov 8, 2023 at 8:09 PM Drouvot, Bertrand
<bertranddrouvot.pg@gmail.com> wrote:
>
> > Unrelated to above, if there is a user slot on standby with the same
> > name which the slot-sync worker is trying to create, then shall it
> > emit a warning and skip the sync of that slot or shall it throw an
> > error?
> >
>
> I'd vote for emit a warning and move on to the next slot if any.
>

But then it could take time for users to know the actual problem and
they probably notice it after failover. OTOH, if we throw an error
then probably they will come to know earlier because the slot sync
mechanism would be stopped. Do you have reasons to prefer giving a
WARNING and skipping creating such slots? I expect this WARNING to
keep getting repeated in LOGs because the consecutive sync tries will
again generate a WARNING.

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Erik Wienhold
Date:
Subject: Re: Fix output of zero privileges in psql
Next
From: Peter Geoghegan
Date:
Subject: Re: [PATCHES] Post-special page storage TDE support