On Wed, Dec 15, 2010 at 15:47, Tom Lane <t...@sss.pgh.pa.us> wrote: > Robert Haas <robertmh...@gmail.com> writes: >> On Wed, Dec 15, 2010 at 9:39 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: >>> Really? Personally I'm quite happy with that default. > >> Why? It seems to me that just leads to, oh, gee, the database isn't >> shutting down, where's the window where I failed to exit a session? > > Yeah, and more to the point, do I want to finish whatever I was doing in > that window? Fast-by-default is a nice hammer to swing, but one day > you'll pound your finger.
The whole question "whatever I was doing in that window" indicates a very limited deployment. In most production deployments, that would mean different machiens, and many different people... As a DBA, I certainly don't want to have to wait around for everybody in my organization to get back from lunch and close their clients.. In reality, more often than not I see the default shutdown turn into a very efficient DOS - nobody can do anything in the database ,and a restart (which is the usual case really - most people don't shut down their db, they restart it - or shutdown/upgrade/start or something like that) that could go in seconds turns into minutes or longer. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
