]> granicus.if.org Git - postgresql/commit
Remember asking for feedback during walsender shutdown.
authorAndres Freund <andres@anarazel.de>
Fri, 29 Apr 2016 05:09:51 +0000 (22:09 -0700)
committerAndres Freund <andres@anarazel.de>
Fri, 29 Apr 2016 05:11:18 +0000 (22:11 -0700)
commit596f936055c562c63696699d03c76e24189dec7c
tree5e42477122ba0b9b9f549533cbb4f6a0508f0862
parent65c2eeb003bfc4e37f504e429bded6f0c0b40d43
Remember asking for feedback during walsender shutdown.

Since 5a991ef8 we're explicitly asking for feedback from the receiving
side when shutting down walsender, if there's not yet replicated
data.

Unfortunately we didn't remember (i.e. set waiting_for_ping_response to
true) having asked for feedback, leading to scenarios in which replies
were requested at a high frequency.

I can't reproduce this problem on my laptop, I think that's because the
problem requires a significant TCP window to manifest due to the
!pq_is_send_pending() condition. But since this clearly is a bug, let's
fix it.  There's quite possibly more wrong than just this though.

While fiddling with WalSndDone(), I rewrote a hard to understand comment
about looking at the flush vs. the write position.

Reported-By: Nick Cleaton, Magnus Hagander
Author: Nick Cleaton
Discussion: CAFgz3kus=rC_avEgBV=+hRK5HYJ8vXskJRh8yEAbahJGTzF2VQ@mail.gmail.com
    CABUevExsjROqDcD0A2rnJ6HK6FuKGyewJr3PL12pw85BHFGS2Q@mail.gmail.com
Backpatch: 9.4, were 5a991ef8 introduced the use of feedback messages
    during shutdown.
src/backend/replication/walsender.c