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

Hi!

On Wed, Mar 4, 2026 at 10:47 AM Andrey Silitskiy
<a.silitskiy@postgrespro.ru> wrote:
> On Wed, 03 Mar 2026 Japin Li <japinli(at)hotmail(dot)com> wrote:
>  > At first glance, wal_sender_shutdown_timeout seems to have the wrong
>  > type.
>
> Fixed.

I've revised this patch fixing grammar in commit message, comments and
documentation.

I think the current patch addresses all the main concerns raised in
the thread.  The patch doesn't unconditionally change the behavior: it
introduces a new GUC, which could be set on per-connection basis, and
also affects physical WAL senders.  The GUC specifies timeout, which
gives user a flexibility.  The default value of the GUC is -1
(disabled).  So, no behavior change by default.  Also, it doesn't
require replication protocol change.  New WalSndDoneImmediate() sends
done message to the receiver just like WalSndDone().  So, existing
clients should be OK.

I'm going to push this if no objections.

------
Regards,
Alexander Korotkov
Supabase