Re: Exit walsender before confirming remote flush in logical replication - Mailing list pgsql-hackers

From Andrey Silitskiy
Subject Re: Exit walsender before confirming remote flush in logical replication
Date
Msg-id 8a250eda-77c2-4872-b675-35513b74b8af@postgrespro.ru
Whole thread Raw
In response to Re: Exit walsender before confirming remote flush in logical replication  (Andrey Silitskiy <a.silitskiy@postgrespro.ru>)
Responses Re: Exit walsender before confirming remote flush in logical replication
List pgsql-hackers
On Mar 30, 2026 Andrey Silitskiy
<a(dot)silitskiy(at)postgrespro(dot)ru>wrote:
 > It is worth noting that in this configuration, the second walsender may
 > terminate due to inactive slot before the wal_sender_shutdown_timeout
 > terminates the process, ...

Updated. In this configuration, in some situations walsender processes
may already have been terminated by the time of fast shutdown.
And in this case, the fast shutdown will be successful, but it will not
be the reason for walsender termination and the logs will be different.
Decided to leave the new shutdown test case, but not check the logs in it.
Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: EXPLAIN: showing ReadStream / prefetch stats
Next
From: Andrew Jackson
Date:
Subject: Re: Add ldapservice connection parameter