From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: smart shutdown at end of transaction (was: Default mode for shutdown) |
Date: | 2012-04-27 18:51:05 |
Message-ID: | CABUevEzHL97QwH0JZ-PT6w_4K0MSSh5rn9WX=eEc7U6k3m86_A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Apr 27, 2012 at 20:48, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
>> On Fri, Apr 27, 2012 at 7:29 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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")
How about "wait" instead of "slow"?
> smart - allow existing transactions to finish (new)
and still default, right?
> fast - kill active queries
> immediate - unclean shutdown
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-04-27 18:56:10 | Re: smart shutdown at end of transaction (was: Default mode for shutdown) |
Previous Message | Tom Lane | 2012-04-27 18:48:27 | Re: smart shutdown at end of transaction (was: Default mode for shutdown) |