Hi
I think that kill will only take effect when the server pays attention - if
it is busy (calculating statistics), then it may not respond immediately.
Regards
Quentin
-----Original Message-----
From: Steve Ruby [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 8 March 2001 5:19 a.m.
To: [EMAIL PROTECTED]
Subject: Re: kill bad query
Steve Ruby wrote:
>
> If I have a connection that executes a bad query shouldn't I
> ALWAYS be able to kill it with "kill <connect num>"?
>
> I have a query that keeps getting stuck, (who knows what
> it is doing) but that State is "statistics"
>
> I can't ever kill it without taking down the server..
>
PS.. this is using 3.23.33 on Linux.. I find that the query is very
slow but will eventually complete, still, can I not kill a query
that will lock tables for hours?
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail
<[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
The information contained in this email is privileged and confidential
and intended for the addressee only. If you are not the intended
recipient, you are asked to respect that confidentiality and not
disclose, copy or make use of its contents. If received in error
you are asked to destroy this email and contact the sender immediately.
Your assistance is appreciated.
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
