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 26b41b30-2484-4fa7-b951-b97805101bd7@postgrespro.ru
Whole thread Raw
In response to Re: Exit walsender before confirming remote flush in logical replication  (Ronan Dunklau <ronan@dunklau.fr>)
List pgsql-hackers
Dear Ronan,
Thanks for participating in the discussion.

On Jan 28, 2026 Ronan Dunklau <ronan(at)dunklau(dot)fr> wrote:
 > ... a timeout for the wait (maybe named wal_sender_stop_timeout ?) would
 > allow for the same usage ...

Sounds like an option.
This is also possible in the current implementation, but your option offers
a simpler interface if we do not plan to add new wallsender completion 
modes.
The naming of the parameter is also a question, because wal_sender_timeout
already exists (which also fits the name wal_sender_stop_timeout quite 
well).
The difference between these parameters may not be obvious to users.
Thoughts?

Regards,
Andrey Silitskiy



pgsql-hackers by date:

Previous
From: Andrey Silitskiy
Date:
Subject: Re: Exit walsender before confirming remote flush in logical replication
Next
From: shveta malik
Date:
Subject: Re: Proposal: Conflict log history table for Logical Replication