postgresql/src/backend/postmaster
Andres Freund f15538cd27 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.pg@gmail.com>
Discussion: https://postgr.es/m/kgng5nrvnlv335evmsuvpnh354rw7qyazl73kdysev2cr2v5zu@m3cfzxicm5kp
2025-01-24 17:08:33 -05:00
..
autovacuum.c Allow changing autovacuum_max_workers without restarting. 2025-01-06 15:01:22 -06:00
auxprocess.c Update copyright for 2025 2025-01-01 11:21:55 -05:00
bgworker.c Update copyright for 2025 2025-01-01 11:21:55 -05:00
bgwriter.c Update copyright for 2025 2025-01-01 11:21:55 -05:00
checkpointer.c checkpointer: Request checkpoint via latch instead of signal 2025-01-24 17:00:10 -05:00
fork_process.c Update copyright for 2025 2025-01-01 11:21:55 -05:00
interrupt.c Update copyright for 2025 2025-01-01 11:21:55 -05:00
launch_backend.c Update copyright for 2025 2025-01-01 11:21:55 -05:00
Makefile Assign a child slot to every postmaster child process 2024-11-14 16:12:28 +02:00
meson.build Update copyright for 2025 2025-01-01 11:21:55 -05:00
pgarch.c Update copyright for 2025 2025-01-01 11:21:55 -05:00
pmchild.c Allow changing autovacuum_max_workers without restarting. 2025-01-06 15:01:22 -06:00
postmaster.c postmaster: Adjust which processes we expect to have exited 2025-01-24 17:08:33 -05:00
startup.c Update copyright for 2025 2025-01-01 11:21:55 -05:00
syslogger.c Update copyright for 2025 2025-01-01 11:21:55 -05:00
walsummarizer.c Update copyright for 2025 2025-01-01 11:21:55 -05:00
walwriter.c Update copyright for 2025 2025-01-01 11:21:55 -05:00