MySQL Bugs: #46046: improve performace of KILL command during fulltext search

Bug #46046	improve performace of KILL command during fulltext search
Submitted:	8 Jul 2009 16:43	Modified:	20 Nov 2013 11:03
Reporter:	Lig Isler-Turmelle	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S4 (Feature request)
Version:		OS:	Any
Assigned to:	Jimmy Yang	CPU Architecture:	Any

Description:
According to the manual one of the things KILL is supposed to do is terminate a query.  And yet there there are definite situations where this just is not happening as advertised (Ex: http://bugs.mysql.com/bug.php?id=19610 http://bugs.mysql.com/bug.php?id=42907). 

I request for KILL to work fast and quick on any query. 

How to repeat:
na

Suggested fix:
unknown

In the current implementation of KILL it does not seem to make fulltext searches "killable" and there is no comment in the documentation that it is NOT at http://dev.mysql.com/doc/refman/5.1/en/kill.html

An example of this is given in http://bugs.mysql.com/bug.php?id=42907 under the entry  [17 Feb 1:18] Miguel Solorzano:

Indeed on machine dual core 64-bit Windows Vista that query arise 50-52% CPU usage, aftera kill the query continues how can see below"...

Indeed, we need a way to make queries killable while they do fulltext search. Or, at least, we should explicitely document that KILL will not work until fulltext search will be finished.

FTS issues are supposed to have been fixed in bug#42907: MULTI-TERM BOOLEAN FULLTEXT QUERY CONTAINING A SINGLE QUOTE FAILS IN 5.1.