Properly initialize write, flush and replay locations in walsender slots
authorMagnus Hagander
Sun, 13 Dec 2015 15:40:37 +0000 (16:40 +0100)
committerMagnus Hagander
Sun, 13 Dec 2015 15:44:04 +0000 (16:44 +0100)
commita1fb84990dc172f21f12a8fb79ab58876e81fe6b
treed213d4221d6eaccfea0f8c12d73a2f4123845aa2
parent5f1de605640578667e97894d846d119a5dc5a31f
Properly initialize write, flush and replay locations in walsender slots

These would leak random xlog positions if a walsender used for backup would
a walsender slot previously used by a replication walsender.

In passing also fix a couple of cases where the xlog pointer is directly
compared to zero instead of using XLogRecPtrIsInvalid, noted by
Michael Paquier.
src/backend/replication/walsender.c