On 31-01-2009 10:23:42 +0100, Martin Kersten wrote:
On 30-01-2009 21:59:15 -0600, Ross Bates wrote:
As to the possibility to kill a client, perhaps we can just create a hook at the MAL level. It is worth to open up a feature request for this, I think. The hooks are available in the kernel to stop a client between individual MAL statements. It requires protocol extensions for out of bound messages, or a secure scheme to open a second connection using the same user credentials to shoot off another. Then a SQL command like "call resetClient()" could be made to do
Fabian Groffen wrote: the trick.
If you login as admin, you can simply use "KILL", otherwise you can't. Simple.
This does not solve the point raised, i.e. to stop instructions in the middle of their processing. This is one of the design issues why MonetDB can be fast, i.e. in the inner loop of bulk operations avoid time checking environment status.
Yes, but it does allow to stop a client earlier than it is now. E.g. it allows you to shoot a client that you want to get off of your system, such as when you bring it down to maintenance mode. When you get tired of waiting, you just shoot the clients that are still connected/idle.