pgsql: postmaster: Adjust which processes we expect to have exited

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: postmaster: Adjust which processes we expect to have exited
Date: 2025-01-24 22:42:08
Message-ID: E1tbSNL-003L6x-RS@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

postmaster: Adjust which processes we expect to have exited

Comments and code stated that we expect checkpointer to have been signalled in
case of immediate shutdown / fatal errors, but didn't treat archiver and
walsenders the same. That doesn't seem right.

I had started digging through the history to see where this oddity was
introduced, but it's not the fault of a single commit.

Instead treat archiver, checkpointer, and walsenders the same.

Reviewed-by: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Discussion: https://postgr.es/m/kgng5nrvnlv335evmsuvpnh354rw7qyazl73kdysev2cr2v5zu@m3cfzxicm5kp

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/f15538cd27d4eeb7d665263a3d7b5700362d7eb0

Modified Files
--------------
src/backend/postmaster/postmaster.c | 28 ++++++++++++++++++----------
1 file changed, 18 insertions(+), 10 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Jeff Davis 2025-01-24 22:59:27 pgsql: Add SQL function CASEFOLD().
Previous Message Tom Lane 2025-01-24 18:20:51 pgsql: Make jsonb casts to scalar types translate JSON null to SQL NULL