From a806b14a1139d3443a7c2c263abb9ff8e4a65694 Mon Sep 17 00:00:00 2001 From: Noah Misch Date: Sat, 8 Jun 2019 10:12:26 -0700 Subject: [PATCH] Update documentation about SIGKILL of postmaster. Removing shared memory and semaphores in response to server start failure often masks the real problem, a live process associated with the data directory; see commit 5a907404b52753c4d6c6a7c21765aeaa42fd6a3b. Since 9.6, it's rarely necessary to kill subprocesses manually. (When it is necessary, that commit's HINT will say as much, in all supported versions.) --- doc/src/sgml/runtime.sgml | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index e053e2ee34..18c11a2bed 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1685,14 +1685,12 @@ $ kill -INT `head -1 /usr/local/pgsql/data/postmaster.pid` - It is best not to use SIGKILL to shut down - the server. Doing so will prevent the server from releasing - shared memory and semaphores, which might then have to be done - manually before a new server can be started. Furthermore, - SIGKILL kills the postgres - process without letting it relay the signal to its subprocesses, - so it will be necessary to kill the individual subprocesses by hand as - well. + It is best not to use SIGKILL to shut down the + server. Doing so will prevent the server from releasing shared memory and + semaphores. Furthermore, SIGKILL kills + the postgres process without letting it relay the + signal to its subprocesses, so it might be necessary to kill the + individual subprocesses by hand as well. -- 2.40.0