rm_cleanup functions need to be allowed to write WAL entries. This oversight

appears to explain the recent reports of "PANIC: cannot make new WAL entries
during recovery".

diff --git a/src/backend/access/transam/xlog.c b/src/backend/access/transam/xlog.c
index d6a9f202e579a74bba32d90201be064bfeef5736..3f5331758afd3a5aa21ba2feed2071804924cc49 100644 (file)
--- a/src/backend/access/transam/xlog.c
+++ b/src/backend/access/transam/xlog.c
@@ -463,6 +463,7 @@ static void readRecoveryCommandFile(void);
 static void exitArchiveRecovery(TimeLineID endTLI,
                                        uint32 endLogId, uint32 endLogSeg);
 static bool recoveryStopsHere(XLogRecord *record, bool *includeThis);
+static void LocalSetXLogInsertAllowed(void);
 static void CheckPointGuts(XLogRecPtr checkPointRedo, int flags);
 
 static bool XLogCheckBuffer(XLogRecData *rdata, bool doPageWrites,
@@ -5758,6 +5759,13 @@ StartupXLOG(void)
        {
                int                     rmid;
 
+               /*
+                * Resource managers might need to write WAL records, eg, to record
+                * index cleanup actions.  So temporarily enable XLogInsertAllowed in
+                * this process only.
+                */
+               LocalSetXLogInsertAllowed();
+
                /*
                 * Allow resource managers to do any required cleanup.
                 */
@@ -5767,6 +5775,9 @@ StartupXLOG(void)
                                RmgrTable[rmid].rm_cleanup();
                }
 
+               /* Disallow XLogInsert again */
+               LocalXLogInsertAllowed = -1;
+
                /*
                 * Check to see if the XLOG sequence contained any unresolved
                 * references to uninitialized pages.