Re:Anatomy of a Crushing
by rimantas on Tuesday March 08, 2011 @04:39PM
(#2302696)
For those in constant fear: http://dev.mysql.com/doc/refman/5.1/en/mysql-tips.html#safe-...
[ Parent
| on HN ]
Ha, I half-remembered this existing and tried to Google my way to it, but to no avail. Thanks so much for the pointer!
In a huge database, even a SELECT with no WHERE clause can tie up considerable resources.
--i-am-a-dummy also limits the number of rows you can SELECT or JOIN.
You can kill it though, use SHOW PROCESSLIST
I always write my WHERE clauses first whenever I do anything on a live dataset.
Re:Anatomy of a Crushing
by SupremumLimit on Wednesday March 09, 2011 @12:21AM
(#2303947)
I always had a rule to do everything inside a transaction. Having to commit a transaction gives you just enough pause to double check what you've done.