Tom Lane wrote:
If you don't mind plastering a "use at your own risk" sign on it, then go for it.
killing a backend is obviously much more "at your own risk" than a descent function.
[...]
What about implementing "kill" as "cancel then exit"? Does that guarantee a safe exit in all cases?
It wouldn't catch *all* the cases where you want to kill a backend, just the ones where the backend is in a cancellable state, but it seems to me that the main usecase is killing an otherwise idle backend that the client doesn't want to let go of. And if the backend isn't cancellable for an extended period, you probably have other problems anyway.
-O
---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
