]> granicus.if.org Git - postgresql/commit
Be less aggressive in asking for feedback of logical walsender clients.
authorAndres Freund <andres@anarazel.de>
Tue, 12 Aug 2014 09:04:50 +0000 (11:04 +0200)
committerAndres Freund <andres@anarazel.de>
Tue, 12 Aug 2014 09:05:46 +0000 (11:05 +0200)
commit423f73df9dcb9fd5b05fb1ed17bd636245bb90f3
treeb0cb6abdc6ac3b9837b155f648ecd27762654aa9
parent700f060528b1485970e6414fbf96aa1f87766a40
Be less aggressive in asking for feedback of logical walsender clients.

When doing logical decoding using START_LOGICAL_REPLICATION in a
walsender process the walsender sometimes was sending out keepalive
messages too frequently. Asking for feedback every time.

WalSndWaitForWal() sends out keepalive messages when it's waiting for
new WAL to be generated locally when it sees that the remote side
hasn't yet flushed WAL up to the local position. That generally is
good but causes problems if the remote side only writes but doesn't
flush changes yet. So check for both remote write and flush position.

Additionally we've asked for feedback to the keepalive message which
isn't warranted when waiting for WAL in contrast to preventing
timeouts because of wal_sender_timeout.

Complaint and patch by Steve Singer.
src/backend/replication/walsender.c