Tom Lane 48913db887 In immediate shutdown, postmaster should not exit till children are gone. ... This adjusts commit 82233ce7ea so that the postmaster does not exit until all its child processes have exited, even if the 5-second timeout elapses and we have to send SIGKILL. There is no great value in having the postmaster process quit sooner, and doing so can mislead onlookers into thinking that the cluster is fully terminated when actually some child processes still survive. This effect might explain recent test failures on buildfarm member hamster, wherein we failed to restart a cluster just after shutting it down with "pg_ctl stop -m immediate". I also did a bit of code review/beautification, including fixing a faulty use of the Max() macro on a volatile expression. Back-patch to 9.4. In older branches, the postmaster never waited for children to exit during immediate shutdowns, and changing that would be too much of a behavioral change.		2015-06-19 14:23:39 -04:00
..
src	In immediate shutdown, postmaster should not exit till children are gone.	2015-06-19 14:23:39 -04:00
bug.template	Stamp HEAD as 9.5devel.	2014-06-10 21:36:13 -04:00
KNOWN_BUGS	Remove extra newlines at end and beginning of files, add missing newlines	2010-08-19 05:57:36 +00:00
Makefile	Remove maintainer-check target, fold into normal build	2013-10-10 20:11:56 -04:00
MISSING_FEATURES	Remove extra newlines at end and beginning of files, add missing newlines	2010-08-19 05:57:36 +00:00
TODO	Update URL.	2008-08-21 20:15:31 +00:00