0001-postmaster-fix-stale-pm_startup-comment.patch
application/octet-stream
Filename: 0001-postmaster-fix-stale-pm_startup-comment.patch
Type: application/octet-stream
Part: 0
Patch
Same data as JSON:
GET /api/v1/attachments/:id/patch
the parsed metadata as JSON — format, series position, per-file stats; never the diff bytes.
API reference →
Format: format-patch
Series: patch 0001
Subject: postmaster: fix stale PM_STARTUP comment
| File | + | − |
|---|---|---|
| src/backend/postmaster/postmaster.c | 3 | 3 |
From 972c14fb9134fdfd76ea6ebcf98a55a945bbc988 Mon Sep 17 00:00:00 2001 From: Ayush Tiwari <ayushtiwari.slg01@gmail.com> Date: Wed, 15 Apr 2026 18:54:56 +0530 Subject: [PATCH] postmaster: fix stale PM_STARTUP comment The comment above the PM_STARTUP startup-process-failure case still says there are no other processes running yet. That is no longer accurate: other postmaster children may already be running by this point. Adjust the comment to describe the current behavior more accurately. --- src/backend/postmaster/postmaster.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/backend/postmaster/postmaster.c b/src/backend/postmaster/postmaster.c index 6e0f41d2661e..d0b2e0bc8d2e 100644 --- a/src/backend/postmaster/postmaster.c +++ b/src/backend/postmaster/postmaster.c @@ -2307,8 +2307,9 @@ process_pm_child_exit(void) /* * Unexpected exit of startup process (including FATAL exit) - * during PM_STARTUP is treated as catastrophic. There are no - * other processes running yet, so we can just exit. + * during PM_STARTUP is treated as catastrophic. While other + * postmaster children may already be running, this leaves the + * system in an unrecoverable state requiring immediate exit. */ if (pmState == PM_STARTUP && StartupStatus != STARTUP_SIGNALED && -- 2.34.1