From 620935ad088d4779ed7fa65f38a876b30e01dee4 Mon Sep 17 00:00:00 2001 From: Alvaro Herrera Date: Wed, 3 Jul 2013 11:04:21 -0400 Subject: [PATCH] Unbreak postmaster restart-after-crash sequence In patch 82233ce7ea42, AbortStartTime wasn't being reset appropriately after the restart sequence, causing subsequent iterations through ServerLoop to malfunction. --- src/backend/postmaster/postmaster.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/backend/postmaster/postmaster.c b/src/backend/postmaster/postmaster.c index 64467cb53c..15fd4c90ea 100644 --- a/src/backend/postmaster/postmaster.c +++ b/src/backend/postmaster/postmaster.c @@ -2594,6 +2594,7 @@ reaper(SIGNAL_ARGS) * Startup succeeded, commence normal operations */ FatalError = false; + AbortStartTime = 0; ReachedNormalRunning = true; pmState = PM_RUN; @@ -4711,6 +4712,7 @@ sigusr1_handler(SIGNAL_ARGS) { /* WAL redo has started. We're out of reinitialization. */ FatalError = false; + AbortStartTime = 0; /* * Crank up the background tasks. It doesn't matter if this fails, -- 2.40.0