You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add lock information to lock timeout error message
Summary:
Currently, on lock timeout, we only give
ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction
which has no information on what type of lock timed out.
This change augments the message with the lock type to say something like
ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction: Timeout on index: test/t1.GEN_CLUST_INDEX
which shows which type of lock timed out as well as the associated object.
There two cases to handle here. For error messages coming from the storage engine, the error is stored onto the transaction, which will get forwarded to the SQL layer for display through `handler::get_error_message`.. For MDL locks in the SQL layer, we are directly using the information in the MDL lock to display the error message.
I didn't touch NDB because I didn't bother getting that to build.
Test Plan: mtr
Reviewers: jkedgar, jtolmer
Reviewed By: jtolmer
Subscribers: ebergen, webscalesql-eng
Differential Revision: https://reviews.facebook.net/D47613
0 commit comments