Von: Tom Lane <tgl@sss.pgh.pa.us>
An: Simon Riggs <simon@2ndQuadrant.com>
CC: Robert Haas <robertmhaas@gmail.com>; Alvaro Herrera <alvherre@commandprompt.com>; Magnus Hagander <magnus@hagander.net>; PostgreSQL-development <pgsql-hackers@postgresql.org>
Gesendet: 20:48 Freitag, 27.April 2012
Betreff: Re: [HACKERS] smart shutdown at end of transaction (was: Default mode for shutdown)
Simon Riggs <
simon@2ndQuadrant.com> writes:
> On Fri, Apr 27, 2012 at 7:29 PM, Tom Lane <
tgl@sss.pgh.pa.us> wrote:
>> No, I'm not happy with that. Smart shutdown is defined to not affect
>> current sessions. I'm fine with having a fourth mode that acts as you
>> suggest (and, probably, even with making it the default); but not with
>> taking away a behavior that people may well be relying on.
> Agreed, but not sure what to call the new mode: "smarter"?
I'm not necessarily opposed to commandeering the name "smart" for the
new behavior, so that what we have to find a name for is the old "smart"
behavior. How about
slow - allow existing sessions to finish (old "smart")
smart - allow existing transactions to finish (new)
fast - kill active queries
immediate - unclean shutdown
regards, tom lane
--
Sent via pgsql-hackers mailing list (
pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers