Kill dead-end children when there's nothing else left
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>
Thu, 14 Nov 2024 14:12:04 +0000 (16:12 +0200)
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>
Thu, 14 Nov 2024 14:12:04 +0000 (16:12 +0200)
commitbb861414fea31073f27aaab75a0ceaf3638d7985
tree693850f21bff362d67ca7276d8cb73245653ae3f
parent18d67a8d7d30884655d65910b82781d9360819a6
Kill dead-end children when there's nothing else left

Previously, the postmaster would never try to kill dead-end child
processes, even if there were no other processes left. A dead-end
backend will eventually exit, when authentication_timeout expires, but
if a dead-end backend is the only thing that's preventing the server
from shutting down, it seems better to kill it immediately. It's
particularly important, if there was a bug in the early startup code
that prevented a dead-end child from timing out and exiting normally.

Includes a test for that case where a dead-end backend previously
prevented the server from shutting down.

Reviewed-by: Andres Freund <andres@anarazel.de>
Discussion: https://www.postgresql.org/message-id/a102f15f-eac4-4ff2-af02-f9ff209ec66f@iki.fi
src/backend/postmaster/postmaster.c
src/test/perl/PostgreSQL/Test/Cluster.pm
src/test/postmaster/meson.build
src/test/postmaster/t/002_start_stop.pl [new file with mode: 0644]