Fix corner-case bug in tracking of latest removed WAL segment during
streaming replication. We used log/seg 0/0 to indicate that no WAL segments
have been removed since startup, but 0/0 is a valid value for the very first
WAL segment after initdb. To make that disambiguous, store
(latest removed WAL segment + 1) in the global variable.
Per report from Matt Chesler, also reproduced by Greg Smith.
Branch
------
REL9_0_STABLE
Details
-------
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=268fecc62cde08c89952c26cb01db8f04a2dc88d
Modified Files
--------------
src/backend/access/transam/xlog.c | 9 ++++++---
src/backend/replication/walsender.c | 2 +-
2 files changed, 7 insertions(+), 4 deletions(-)
