Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
i have an issue with my current database with mysql.
i have over 100 connection waiting on a select record. when i execute:
show processlist;
the select query is a big query and the others are smaler queries and inserts, updates.
i have one database with 100 tables and the select is using 5 joins.
is there a way to temporary stop the process and let the other processes run, once all the processes are completed, then the select can continue running?
i will recommend to let the query do what it needs to do, if you stop any or kill processses or queries you might have data integrity errors which can lead to major errors.
BookOfZeus and tfb785 are right, first of all you probably have indexes errors. the explain will tell you what exactly is the problem and what to look for. for example if you have 5 joins and you get row counts like, 100,000 and 100 and 1 and 1 and 1 you will multiple 100,000 * 100 which can be super slow.
read carefully what the explain tells you and optimize your query based on it.
innodb can be a good option if you if the tables are accessed very often because its row locking insted of table locking for myisam.
I would say first try to optimize your query, maybe you wont need to alter your table engine to fix the issue. if you still have issues then you might consider moving to innodb.