From: Heikki Linnakangas <heikki.linnakangas@iki.fi>
Date: Tue, 8 Apr 2014 11:47:24 +0000 (+0300)
Subject: Fix hot standby bug with GiST scans.
X-Git-Tag: REL9_0_18~61
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=d034e9b3be3f9a2a2b85a4cb67f24c246d37f117;p=postgresql

Fix hot standby bug with GiST scans.

Don't reset the rightlink of a page when replaying a page update record.
This was a leftover from pre-hot standby days, when it was not possible to
have scans concurrent with WAL replay. Resetting the right-link was not
necessary back then either, but it was done for the sake of tidiness. But
with hot standby, it's wrong, because a concurrent scan might still need it.

Backpatch all versions with hot standby, 9.0 and above.
---

diff --git a/src/backend/access/gist/gistxlog.c b/src/backend/access/gist/gistxlog.c
index e7c3e2dd75..d044f18484 100644
--- a/src/backend/access/gist/gistxlog.c
+++ b/src/backend/access/gist/gistxlog.c
@@ -253,7 +253,6 @@ gistRedoPageUpdateRecord(XLogRecPtr lsn, XLogRecord *record, bool isnewroot)
 		 */
 		GistPageSetLeaf(page);
 
-	GistPageGetOpaque(page)->rightlink = InvalidBlockNumber;
 	PageSetLSN(page, lsn);
 	PageSetTLI(page, ThisTimeLineID);
 	MarkBufferDirty(buffer);