Skip to content

Commit 620935a

Browse files
committed
Unbreak postmaster restart-after-crash sequence
In patch 82233ce, AbortStartTime wasn't being reset appropriately after the restart sequence, causing subsequent iterations through ServerLoop to malfunction.
1 parent 00a7767 commit 620935a

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

src/backend/postmaster/postmaster.c

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2594,6 +2594,7 @@ reaper(SIGNAL_ARGS)
25942594
* Startup succeeded, commence normal operations
25952595
*/
25962596
FatalError = false;
2597+
AbortStartTime = 0;
25972598
ReachedNormalRunning = true;
25982599
pmState = PM_RUN;
25992600

@@ -4711,6 +4712,7 @@ sigusr1_handler(SIGNAL_ARGS)
47114712
{
47124713
/* WAL redo has started. We're out of reinitialization. */
47134714
FatalError = false;
4715+
AbortStartTime = 0;
47144716

47154717
/*
47164718
* Crank up the background tasks. It doesn't matter if this fails,

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy