MySQL
keyboard_arrow_down 295 guides
chevron_leftServer settings Cookbook
check_circle
Mark as learned thumb_up
0
thumb_down
0
chat_bubble_outline
0
auto_stories new
settings
Ending problematic queries in MySQL
schedule Mar 5, 2023
Last updated local_offer
Tags MySQL
tocTable of Contents
expand_more Check out the interactive map of data science
You can end problematic processes in MySQL by using the KILL statement:
KILL 12345;
Query OK, 0 rows affected (0.02 sec)
12345 in the above example is the process number of the problematic process. If you do not know this you can confirm this using the below command which shows all running processes:
SHOW PROCESSLIST;
Example
To confirm all running processes:
SHOW PROCESSLIST;
+----+------+----------------+--------+---------+------+-------+------------------+| Id | User | Host | db | Command | Time | State | Info |+----+------+----------------+--------+---------+------+-------+------------------+| 10 | root | localhost:4049 | people | Sleep | 39 | | NULL || 13 | root | localhost:4451 | people | Query | 0 | NULL | SHOW PROCESSLIST |+----+------+----------------+--------+---------+------+-------+------------------+
To kill process with Id = 10:
KILL 10;
Query OK, 0 rows affected (0.00 sec)
To confirm process with Id = 10 has been ended:
SHOW PROCESSLIST;
+----+------+----------------+--------+---------+------+-------+------------------+| Id | User | Host | db | Command | Time | State | Info |+----+------+----------------+--------+---------+------+-------+------------------+| 13 | root | localhost:4451 | people | Query | 0 | NULL | SHOW PROCESSLIST |+----+------+----------------+--------+---------+------+-------+------------------+
Published by Arthur Yanagisawa
Edited by 0 others
Did you find this page useful?
thumb_up
thumb_down
Comment
Citation
Ask a question or leave a feedback...
thumb_up
0
thumb_down
0
chat_bubble_outline
0
settings
Enjoy our search
Hit / to insta-search docs and recipes!
