Re: Questionable ping logic in LogicalRepApplyLoop
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: pgsql-hackers@lists.postgresql.org,
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
Petr Jelinek <petr@2ndquadrant.com>
Date: 2020-09-04T21:41:11Z
Lists: pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes: > ... oh look! commit 3f60f690fac1 moved last_recv_timestamp without > realizing that ping_sent had to get the same treatment. Hah, I wondered if something like that had happened, but I didn't get around to excavating in the git history yet. Thanks for doing so. Will push a fix later. regards, tom lane
Commits
-
Fix over-eager ping'ing in logical replication receiver.
- 9b81a30f924c 13.0 landed
- c8746f999ea2 14.0 landed
- 9b8a8516ed2e 10.15 landed
- 9b47ee6e7cba 12.5 landed
- 7156a0eac3af 11.10 landed
-
Fix timeout handling in logical replication worker
- 3f60f690fac1 13.0 cited