| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| 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:56:10 |
| Message-ID: | 25145.1335552970@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Fri, Apr 27, 2012 at 20:48, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> 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"?
I kinda liked "slow" vs "fast", but if you think that's too cute ...
("wait" doesn't seem very good, though, since all these except immediate
are waiting, just for different things.)
>> smart - allow existing transactions to finish (new)
> and still default, right?
Right.
>> fast - kill active queries
>> immediate - unclean shutdown
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-04-27 18:57:53 | Re: smart shutdown at end of transaction (was: Default mode for shutdown) |
| Previous Message | Magnus Hagander | 2012-04-27 18:51:05 | Re: smart shutdown at end of transaction (was: Default mode for shutdown) |