Re: smart shutdown at end of transaction (was: Default mode for shutdown) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: smart shutdown at end of transaction (was: Default mode for shutdown)
Date
Msg-id 29545.1335564596@sss.pgh.pa.us
Whole thread Raw
In response to Re: smart shutdown at end of transaction (was: Default mode for shutdown)  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: smart shutdown at end of transaction (was: Default mode for shutdown)  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> It seems we need another signal for the new mode, and the obvious
> candidate is SIGUSR2.  But what shall the mapping look like?

> [Choice #1] SIGUSR2 -> slow, SIGTERM -> smart, SIGINT -> fast, SIGQUIT
> -> immediate
> [Choice #2] SIGTERM -> slow, SIGUSR2 -> smart, SIGINT -> fast, SIGQUIT
> -> immediate

SIGTERM needs to correspond to a fairly aggressive shutdown mode,
since (at least on some systems) init will send that during the system
shutdown sequence, shortly before escalating to SIGKILL.  So I think
choice #2 is not sensible at all.

If we were willing to consider wholesale breakage of any scripts that
send these signals directly, I'd almost consider that it should be
SIGUSR2, SIGINT, SIGTERM, SIGQUIT.  But that might be more churn than
we want.  Keeping SIGTERM attached to the default/"smart" shutdown mode
seems like a reasonable compromise.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: 9.2 release notes, beta time?
Next
From: "Kevin Grittner"
Date:
Subject: Re: Re: xReader, double-effort (was: Temporary tables under hot standby)