Record lock, heap no 3 PHYSICAL RECORD: n_fields 3 compact format info bits 32 RECORD LOCKS space id 40 page no 3 n bits 80 index PRIMARY of table `test`.`t` trx id 846 lock_mode X locks rec but not gap waiting *** (2) WAITING FOR THIS LOCK TO BE GRANTED: RECORD LOCKS space id 40 page no 3 n bits 80 index PRIMARY of table `test`.`t` trx id 846 lock_mode X locks rec but not gap MySQL thread id 39, OS thread handle 139985942361856, query id 840 localhost root Updating TRANSACTION 846, ACTIVE 25 sec starting index readģ lock struct(s), heap size 1136, 2 row lock(s), undo log entries 1 Record lock, heap no 2 PHYSICAL RECORD: n_fields 3 compact format info bits 32 RECORD LOCKS space id 40 page no 3 n bits 80 index PRIMARY of table `test`.`t` trx id 847 lock_mode X locks rec but not gap waiting *** (1) WAITING FOR THIS LOCK TO BE GRANTED: MySQL thread id 46, OS thread handle 139985942054656, query id 839 localhost root Updating LOCK WAIT 4 lock struct(s), heap size 1136, 3 row lock(s), undo log entries 1 TRANSACTION 847, ACTIVE 10 sec starting index read The full Deadlock situation is shown with the following command: So how you can find the other part of the problem? But a deadlock is always a problem between 2 different connections. If your application receives this error message you know where in your application you have a problem. First of all, Deadlocks are usually an application problem, not a database problem! The database itself manifests the application problem with the following message which is sent to the application as an error:ĮRROR 1213 (40001): Deadlock found when trying to get lock try restarting transaction We get ever and ever again customer requests concerning Deadlocks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |