On Fri, Apr 27, 2012 at 8:36 PM, Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> wrote:
> All the modes indeed wait (except for immediate), so I think it would make > sense to define the modes in terms of *what* they wait for. > > wait sessions - allow existing sessions to finish (old "smart") > wait transactions - allow existing transactions to finish (new) > wait checkpoint - kill active queries > wait none - unclean shutdown > > Hmm, the latter two are perhaps a bit confusing. So maybe: > > wait_sessions - allow existing sessions to finish (old "smart") > wait_transactions - allow existing transactions to finish (new) > > fast - kill active queries > immediate - unclean shutdown > > Just thinking out loud here.. +1 Wonderfully clear, little need to check the docs to see what the terms actually mean. New names for both allow us to deprecate use of "smart", since it was a silly term anyway. We keep smart for one more release==wait_sessions, then throw an error in later releases. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
