If we don't have a backup-end-location, don't claim we've reached it.

This was apparently a typo, which caused recovery to think that it
immediately reached the end of backup, and allowed the database to start
up too early.

Reported by Jeff Janes. Backpatch to 9.2, where this code was introduced.

diff --git a/src/backend/access/transam/xlog.c b/src/backend/access/transam/xlog.c
index 3d6046eacfd287124ef2dd7541e33de40384ca1f..9328ad38f4d107714e068d910e09bfd1a3d5b551 100644 (file)
--- a/src/backend/access/transam/xlog.c
+++ b/src/backend/access/transam/xlog.c
@@ -6763,7 +6763,7 @@ StartupXLOG(void)
                /* Pop the error context stack */
                error_context_stack = errcontext.previous;
 
-               if (!XLogRecPtrIsInvalid(ControlFile->backupStartPoint) &&
+               if (!XLogRecPtrIsInvalid(ControlFile->backupEndPoint) &&
                    XLByteLE(ControlFile->backupEndPoint, EndRecPtr))
                {
                    /*