Timeline for Why does that query cause lock wait timeouts?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 6, 2017 at 23:40 | history | tweeted | twitter.com/StackDBAs/status/894342500709797888 | ||
| Aug 4, 2017 at 16:09 | history | edited | RolandoMySQLDBA | Added deadlock and locking tags since query causes deadlocks; removed php tag | |
| May 23, 2017 at 12:40 | history | edited | CommunityBot | replaced http://stackoverflow.com/ with https://stackoverflow.com/ | |
| Mar 21, 2013 at 10:41 | history | edited | RolandoMySQLDBA | edited tags | |
| Mar 21, 2013 at 10:40 | answer | added | RolandoMySQLDBA | timeline score: 9 | |
| Mar 21, 2013 at 9:19 | comment | added | BurninLeo | Thank you for the clarification regarding timeouts and deadlocks. As the deadlock is at the same time as the timeout errors, I think the timeouts were caused by this deadlock. Sorry for clipping the output, I am not yet very used to the MySQL/InnoDb status information - the missing information was complemented, now. | |
| Mar 21, 2013 at 9:17 | history | edited | BurninLeo | CC BY-SA 3.0 | Included more information |
| Mar 21, 2013 at 1:53 | comment | added | Michael - sqlbot | A "lock wait timeout" and a "deadlock" are two completely different things, and a deadlock is about the timing of events from more than one client thread, not "that query." It's "that query" and at least one other query from another thread, and almost certainly prior queries within the same transaction. Unfortunately, you have not posted all of the relevant output from SHOW ENGINE INNODB STATUS for this event... which would be everything from "LATEST DETECTED DEADLOCK" down through "WE ROLL BACK TRANSACTION..." | |
| Mar 21, 2013 at 1:24 | history | migrated | from stackoverflow.com (revisions) | ||
| Mar 20, 2013 at 20:09 | history | asked | BurninLeo | CC BY-SA 3.0 |