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 6ed7f4ed-aac1-4ce9-a692-7062a4bb07f6@postgrespro.ru
Whole thread Raw
In response to Re: Exit walsender before confirming remote flush in logical replication  (Ronan Dunklau <ronan@dunklau.fr>)
Responses Re: Exit walsender before confirming remote flush in logical replication
List pgsql-hackers
On Feb 10, 2026 Ronan Dunklau <ronan(at)dunklau(dot)fr> wrote:
 > - however, if one were to stop the service before doing a pg_upgrade,
 > they would have no other choice than either disable the behaviour
 > entirely (by switching to wait_flush) or fail the upgrade if a logical
 > replication slot is pending changes.

I agree with you, this idea is more flexible. So I changed the interface
from the one discussed in this thread from the very beginning to a timeout.
Propose an updated patch.

Best Regards,
Andrey
Attachment

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row
Next
From: Chao Li
Date:
Subject: Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access)