Re: Non working timeout detection in logical worker
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Julien Rouhaud <rjuju123@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Jehan Guillaume De Rorthais ioguix <ioguix@free.fr>
Date: 2019-10-18T05:32:15Z
Lists: pgsql-hackers
On Thu, Oct 17, 2019 at 08:00:15PM +0200, Julien Rouhaud wrote: > Jehan-Guillaume (in Cc) reported me today a problem with logical > replication, where in case of network issue the walsender is correctly > terminating at the given wal_sender_timeout but the logical worker > kept waiting indefinitely. > > The issue is apparently a simple thinko, the timestamp of the last > received activity being unconditionally set at the beginning of the > main processing loop, making any reasonable timeout setting > ineffective. Trivial patch to fix the problem attached. Right, good catch. That's indeed incorrect. The current code would just keep resetting the timeout if walrcv_receive() returns 0 roughly once per NAPTIME_PER_CYCLE. The ping sent to the server once reaching half of wal_receiver_timeout was also broken because of that. In short, applied and back-patched down to 10. -- Michael
Commits
-
Fix timeout handling in logical replication worker
- 47698b4b62e3 10.11 landed
- feed5ee4753a 11.6 landed
- 04510dbe34b9 12.1 landed
- 3f60f690fac1 13.0 landed