aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/postgres_fdw.c
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2014-03-06 21:13:38 +0200
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2014-03-06 21:40:50 +0200
commitdcd1131c83a3fff824f0fc0a62a61a1e03282da5 (patch)
tree3db69b78151b97baa9e33801061d0934dffce595 /contrib/postgres_fdw/postgres_fdw.c
parent3973034e6dc599de2203ed812f783a57b63dce5c (diff)
downloadpostgresql-dcd1131c83a3fff824f0fc0a62a61a1e03282da5.tar.gz
postgresql-dcd1131c83a3fff824f0fc0a62a61a1e03282da5.zip
Send keepalives from walsender even when busy sending WAL.
If walsender doesn't hear from the client for the time specified by wal_sender_timeout, it will conclude the connection or client is dead, and disconnect. When half of wal_sender_timeout has elapsed, it sends a ping to the client, leaving it the remainig half of wal_sender_timeout to respond. However, it only checked if half of wal_sender_timeout had elapsed when it was about to sleep, so if it was busy sending WAL to the client for long enough, it would not send the ping request in time. Then the client would not know it needs to send a reply, and the walsender will disconnect even though the client is still alive. Fix that. Andres Freund, reviewed by Robert Haas, and some further changes by me. Backpatch to 9.3. Earlier versions relied on the client to send the keepalives on its own, and hence didn't have this problem.
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions