<p dir="ltr">The case where I wanted "routine" shutdown immediate (and I'm not sure I ever actually got it) was when we
wereusing IBM HA/CMP, where I wanted a "terminate with a fair bit of prejudice".<p dir="ltr">If we know we want to
"switchright away now", immediate seemed pretty much right. I was fine with interrupting user sessions, and there
wasn'tas much going on in the way of system background stuff back then.<p dir="ltr">I wasn't keen on waiting on much of
anything. The background writer ought to be keeping things from being too desperately out of date.<p dir="ltr">If
there'sstuff worth waiting a few seconds for, I'm all ears.<p dir="ltr">But if I have to wait arbitrarily long, colour
meunhappy.<p dir="ltr">If I have to distinguish, myself, between a checkpoint nearly done flushing and a backend that's
stuckwaiting forlornly for filesystem access, I'm inclined to "kill -9" and hope recovery doesn't take *too* long on
thenext node...<p dir="ltr">If shutting a server down in an emergency situation requires a DBA to look in, as opposed
toinit.d doing its thing, I think that's pretty much the same problem too.
