Re: Exit walsender before confirming remote flush in logical replication

Dear Hayato,
Thanks for your comments! Updated the patch.

On Jan 15, 2026 at 11:48 AM  Hayato Kuroda
<kuroda(dot)hayato(at)fujitsu(dot)com> wrote:
 > I think we can just use stop() because it internally runs `pg_ctl stop`
 > and that command waits till the wait is finished by default. I feel it
 > is dangerous to determine timeout to 5sec because the test can work on
 > very poor environment.

ok_with_timeout was added because it allows to output a more reasonable
log in case of a problem from this thread: "Failed test 'Successful fast
shutdown of server with empty output buffers (timed out after 5 seconds)'"
instead of the usual "pg_ctl stop failed".  But now I noticed that the
standard timeout  is triggered earlier, and when setting a timeout in this
function greater than the standard PGCTLTIMEOUT, only "pg_ctl stop failed"
will be written. Perhaps it is reasonable to remove these functions.

 > Also, not sure, how can we ensure the buffer is full here? Also, even
 > if we have the way to check, the size may be quite platform depending.
 > I think it may be better to test both streaming and logical replication
 > instead of testing empty/full output buffer. Thought?

Initially, a second test case was added to show that previous patches
did not fix the problem of hanging in case of full buffers. I agree that
it may depend on the platform, but I can't think of a way to guarantee this,
even though the test case seems useful for checking the new mode.
Test contains only the case of logical replication, since so far I'm not
sure how to reproduce guaranteed flush delay on a physical replica in the
test. Any ideas?

Regards,
Andrey Silitskiy