pgsql: Fix elog(FATAL) before PostmasterMain() or just after fork(). - Mailing list pgsql-committers

From Noah Misch
Subject pgsql: Fix elog(FATAL) before PostmasterMain() or just after fork().
Date
Msg-id E1tL8Bm-002657-D6@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix elog(FATAL) before PostmasterMain() or just after fork().

Since commit 97550c0711972a9856b5db751539bbaf2f88884c, these failed with
"PANIC:  proc_exit() called in child process" due to uninitialized or
stale MyProcPid.  That was reachable if close() failed in
ClosePostmasterPorts() or setlocale(category, "C") failed, both
unlikely.  Back-patch to v13 (all supported versions).

Discussion: https://postgr.es/m/20241208034614.45.nmisch@google.com

Branch
------
REL_13_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/6151769f6ef540a71c131165d27426a0bcd1c009

Modified Files
--------------
src/backend/main/main.c               | 2 ++
src/backend/postmaster/fork_process.c | 2 ++
src/backend/postmaster/postmaster.c   | 3 +--
3 files changed, 5 insertions(+), 2 deletions(-)


pgsql-committers by date:

Previous
From: Noah Misch
Date:
Subject: pgsql: Fix elog(FATAL) before PostmasterMain() or just after fork().
Next
From: Tom Lane
Date:
Subject: pgsql: Doc: add some commentary about ExecutorRun's NoMovement special