summaryrefslogtreecommitdiff
path: root/src/backend/replication/walreceiver.c
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2013-01-17 23:12:30 +0200
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2013-01-17 23:45:45 +0200
commit3684a534efbd2ffd72e2c4cbd21f9752be3efaf1 (patch)
tree52da979cbedcbea664a4e7591deb1bf80b5ccc5f /src/backend/replication/walreceiver.c
parent279628a0a7cf582f7dfb68e25b7b76183dd8ff2f (diff)
I added a result set to START_STREAMING command, but neglected walreceiver.
The patch to allow pg_receivexlog to switch timeline added a result set after copy has ended in START_STREAMING command, to return the next timeline's ID to the client. But walreceived didn't get the memo, and threw an error on the unexpected result set. Fix.
Diffstat (limited to 'src/backend/replication/walreceiver.c')
-rw-r--r--src/backend/replication/walreceiver.c4
1 files changed, 3 insertions, 1 deletions
diff --git a/src/backend/replication/walreceiver.c b/src/backend/replication/walreceiver.c
index 16cf9444a57..444be9463bc 100644
--- a/src/backend/replication/walreceiver.c
+++ b/src/backend/replication/walreceiver.c
@@ -431,7 +431,9 @@ WalReceiverMain(void)
{
ereport(LOG,
(errmsg("replication terminated by primary server"),
- errdetail("End of WAL reached on timeline %u", startpointTLI)));
+ errdetail("End of WAL reached on timeline %u at %X/%X",
+ startpointTLI,
+ (uint32) (LogstreamResult.Write >> 32), (uint32) LogstreamResult.Write)));
endofwal = true;
break;
}