Re: synchronized_standby_slots behavior inconsistent with quorum-based synchronous replication - Mailing list pgsql-hackers

From Alexander Kukushkin
Subject Re: synchronized_standby_slots behavior inconsistent with quorum-based synchronous replication
Date
Msg-id CAFh8B=n0n5Zj0DDSQ9E5cznY85VgU1wwgfpAULaLZpOaNzvv4w@mail.gmail.com
Whole thread
In response to Re: synchronized_standby_slots behavior inconsistent with quorum-based synchronous replication  (shveta malik <shveta.malik@gmail.com>)
Responses Re: synchronized_standby_slots behavior inconsistent with quorum-based synchronous replication
List pgsql-hackers
Hi,

On Thu, 26 Feb 2026 at 09:45, shveta malik <shveta.malik@gmail.com> wrote:

As suggested in [1], IMO, it is a reasonably good idea for
'synchronized_standby_slots' to DEFAULT to the value of
'synchronous_standby_names'. That way, even if the user missed to
configure 'synchronized_standby_slots' explicitly, we would still have
reasonable protection in place.

Hmm.
synchronous_standby_names contains application_names, while synchronized_standby_slots contains names of physical replication slots.
These are two different things, and in fact sync replication doesn't even require to use replication slots.
What is worse, even when all standbys use physical replication slots there is no guarantee that values in synchronous_standby_names will match physical slot names.

Regards,
--
Alexander Kukushkin

pgsql-hackers by date:

Previous
From: Jakub Wartak
Date:
Subject: Re: Add errdetail() with PID and UID about source of termination signal
Next
From: Andrei Lepikhov
Date:
Subject: Re: Skipping schema changes in publication