diff options
| author | Robert Haas | 2011-03-25 15:23:39 +0000 |
|---|---|---|
| committer | Robert Haas | 2011-03-25 15:28:16 +0000 |
| commit | 30f6136f28a6bf9eedcbf41038d5b021169bc0b9 (patch) | |
| tree | 7f3f8e7300eda75915165e0c66ff804e63740177 | |
| parent | 01dd34d55ad53117c2d756da7f65b6fa07a303aa (diff) | |
Make walreceiver send a reply after receiving data but before flushing it.
It originally worked this way, but was changed by commit
a8a8a3e0965201df88bdfdff08f50e5c06c552b7, since which time it's been impossible
for walreceiver to ever send a reply with write_location and flush_location
set to different values.
| -rw-r--r-- | src/backend/replication/walreceiver.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/src/backend/replication/walreceiver.c b/src/backend/replication/walreceiver.c index 47a980db20..f6259e4e30 100644 --- a/src/backend/replication/walreceiver.c +++ b/src/backend/replication/walreceiver.c @@ -317,6 +317,9 @@ WalReceiverMain(void) while (walrcv_receive(0, &type, &buf, &len)) XLogWalRcvProcessMsg(type, buf, len); + /* Let the master know that we received some data. */ + XLogWalRcvSendReply(); + /* * If we've written some records, flush them to disk and let the * startup process and primary server know about them. |