On Jan 30, 2026, at 14:59, Shinya Kato <shinya11.kato@gmail.com> wrote:

Hi hackers,

I have noticed an issue where backends waiting for synchronous
replication are not woken up immediately when the number of required
synchronous standbys is reduced in a multiple synchronous standby
environment.

When synchronousstandbynames is updated to require fewer standbys
(for example, changing from "FIRST 2 (s1, s2)" to "FIRST 1 (s1)"), the
backends currently waiting for replication remain blocked even after a
config reload (SIGHUP). They are only released when a new message
eventually arrives from a standby, despite the fact that the new
requirements are already satisfied.

The attached patch adds SyncRepReleaseWaiters() calls within
walsender.c immediately after the configuration is reloaded and
SyncRepInitConfig() is called. This ensures that any backends whose
waiting conditions are now met by the new configuration are released
without unnecessary delay.

Thoughts?

--
Best regards,
Shinya Kato
NTT OSS Center

<v1-0001-Wake-up-backends-immediately-when-sync-standbys-d.patch>

static void
WalSndHandleConfigReload(void)
{
    if (!ConfigReloadPending)
        return;

    ConfigReloadPending = false;
    ProcessConfigFile(PGC_SIGHUP);
    SyncRepInitConfig();

    if (!am_cascading_walsender)
        SyncRepReleaseWaiters();
}