Searching Data - Mastering phpMyAdmin 3.4 for Effective MySQL Management - page 167

Stopping an errant query
Suppose we launch a complex search and notice that the browser is waiting for the
results. This might happen with a database search but also with a single-table search.
We can instruct the browser to stop but this will only tell the web server to cease
handling our request. However, at this point the MySQL server process is busy,
possibly doing a complex join or a full table scan. Here is a method to stop this
errant query:
1. We open a different browser (for example, the errant query was launched via
Firefox and we open Internet Explorer).
2. We log in via phpMyAdmin to MySQL with the same account.
3. On the home page, we click on Processes .
4. At this point, we should see a process identified by Query under the
Command column and containing the errant query (other than SHOW
PROCESSLIST which is not the one to kill).
5. We click on Kill for this process.
6. To verify, we can immediately click again on Processes and the chosen
process should now be identified as Killed instead of Query .
Summary
In this chapter, we took an overview of single table searches with "query by example"
criteria and additional criteria specification—selecting displayed values and ordering
results. We also looked at wildcard searches and full database search.
The next chapter will explain how to perform the operations on tables, for example,
changing a table's attributes, such as its storage engine. The subjects of repairing and
optimizing tables are covered in this chapter as well.