Properly initialize write, flush and replay locations in walsender slots

Magnus Hagander <magnus@hagander.net>

Commit: a9c56ff0e1f19fd6c2e48cfe44407c8cb8c4fbd5
Author: Magnus Hagander <magnus@hagander.net>
Date: 2015-12-13T15:43:35Z
Releases: 9.5.0
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.

Files

PathChange+/−
src/backend/replication/walsender.c modified +6 −3