maybe we could use (a bit complex, but nice):
KILL QUERY_ID IN (SELECT QUERY_ID FROM information_schema.PROCESSLIST WHERE ...)
or
KILL THREAD_ID IN (SELECT id FROM information_schema.PROCESSLIST WHERE ...)
or
KILL USER IN (SELECT user FROM information_schema.PROCESSLIST WHERE ...)
__
uhmmm i didn't think about the if_idle, it was a mail at maria-discuss
that send the patch of google mysql (must check if i'm wrong), and i
ported the patch to mariadb code
the state='' could be really nice, an very good idea =]
2013/8/19 Eric Bergen :
> If you're going to add support for kil
If you're going to add support for killing queries in a specific state
then why not just add the ability to pass in a state? I can see some
use cases for killing queries in a specific state that are more useful
than sleep.
Off the top of my head:
Killing a query while it is waiting for table lock.
Hi guys, i sent some patchs, could anyone check it?
it have some things to do:
query syntax isn't in the MDEV-4911, i did a QUERY_ID instead of a more
comlpex syntax (since i never used bison before :P )
the query_id works, but i need a new error message ( "Unknown query id: %")
well i didn't ma
4 matches
Mail list logo
