aboutsummaryrefslogtreecommitdiff
path: root/src/backend/tcop/postgres.c
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2014-08-12 11:04:50 +0200
committerAndres Freund <andres@anarazel.de>2014-08-12 11:04:50 +0200
commit41d5f8ad734f28ca425636d5ac4c8ea9c29002a5 (patch)
tree5d55aadb3dd0a9d76c29b173e6ef9d47a821fcef /src/backend/tcop/postgres.c
parent51222a176624e8529143f26f43da200c5beb0e9e (diff)
downloadpostgresql-41d5f8ad734f28ca425636d5ac4c8ea9c29002a5.tar.gz
postgresql-41d5f8ad734f28ca425636d5ac4c8ea9c29002a5.zip
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.
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions