pgsql: Properly initialize write, flush and replay locations in walsend

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Properly initialize write, flush and replay locations in walsend
Date: 2015-12-13 16:02:07
Message-ID: E1a8967-0003MF-DT@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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.

Branch
------
REL9_3_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/a1fb84990dc172f21f12a8fb79ab58876e81fe6b

Modified Files
--------------
src/backend/replication/walsender.c | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2015-12-13 17:37:18 Re: pgsql: Fix bug leading to restoring unlogged relations from empty files
Previous Message Robert Haas 2015-12-13 02:22:09 Re: [COMMITTERS] pgsql: Handle policies during DROP OWNED BY