| Bug #51120 | Reveal problem query in large transaction COMMIT hang | ||
|---|---|---|---|
| Submitted: | 11 Feb 2010 21:02 | Modified: | 14 Jan 2013 17:52 |
| Reporter: | Jonathon Coombes | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Logging | Severity: | S4 (Feature request) |
| Version: | OS: | Any | |
| Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
| Tags: | commit, innodb, locking, transaction | ||
[11 Feb 2010 21:02]
Jonathon Coombes
[14 Jan 2013 17:52]
MySQL Verification Team
Surely this can be done with appropriate performance_schema queries in 5.6? http://dev.mysql.com/doc/refman/5.6/en/events-statements-history-long-table.html
