diff options
| author | Andres Freund <andres@anarazel.de> | 2025-01-24 17:00:10 -0500 |
|---|---|---|
| committer | Andres Freund <andres@anarazel.de> | 2025-01-24 17:08:33 -0500 |
| commit | f15538cd27d4eeb7d665263a3d7b5700362d7eb0 (patch) | |
| tree | a6c4bc3ded67a8b5564c30b4bd1b99f025239057 /src/backend/utils/adt/oracle_compat.c | |
| parent | 463a2ebd9fda4fa94833838d0a372f7fd53b5b8a (diff) | |
| download | postgresql-f15538cd27d4eeb7d665263a3d7b5700362d7eb0.tar.gz postgresql-f15538cd27d4eeb7d665263a3d7b5700362d7eb0.zip | |
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
Diffstat (limited to 'src/backend/utils/adt/oracle_compat.c')
0 files changed, 0 insertions, 0 deletions