InnoDB INFORMATION_SCHEMA Transaction and Locking Information 3306 15.15.2.2 InnoDB Lock and Lock-Wait Information Note This section describes locking information as exposed by the Performance Schema  data_locks  and  data_lock_waits  tables, which supersede the  INFORMATION_SCHEMA INNODB_LOCKS  and  INNODB_LOCK_WAITS tables in MySQL 8.0. For similar discussion written in terms of the older INFORMATION_SCHEMA  tables, see InnoDB Lock and Lock-Wait Information, in MySQL 5.7 Reference Manual. When a transaction updates a row in a table, or locks it with  SELECT FOR UPDATE ,  InnoDB  establishes a list or queue of locks on that row. Similarly,  InnoDB  maintains a list of locks on a table for table-level locks. If a second transaction wants to update a row or lock a table already locked by a prior transaction in an incompatible mode,  InnoDB  adds a lock request for the row to the corresponding queue. For a lock to be The following table shows the contents of the  data_locks  table for a system running a heavy workload. requesting trx id requested lock id blocking trx id blocking lock id 77F 77F:806 77E 77E:806 77F 77F:806 77D 77D:806 77F 77F:806 77B 77B:806 77E 77E:806 77D 77D:806 77E 77E:806 77B 77B:806 77D 77D:806 77B 77B:806 77B 77B:733:12:1 77A 77A:733:12:1 E56 E56:743:6:2 E55 E55:743:6:2 E55 E55:743:38:2 19C 19C:743:38:2 lock id lock trx id lock mode lock type lock schema lock table lock index lock data 77F:806 77F AUTO_INC TABLE test t09 NULL NULL 77E:806 77E AUTO_INC TABLE test t09 NULL NULL 77D:806 77D AUTO_INC TABLE test t09 NULL NULL 77B:806 77B AUTO_INC TABLE test t09 NULL NULL 77B:733:12:1 77B X RECORD test t09 PRIMARY supremum pseudo- record 77A:733:12:1 77A X RECORD test t09 PRIMARY supremum pseudo- record E56:743:6:2 E56 S RECORD test t2 PRIMARY 0, 0 E55:743:6:2 E55 X RECORD test t2 PRIMARY 0, 0 E55:743:38:2 E55 S RECORD test t2 PRIMARY 1922, 1922 19C:743:38:2 19C X RECORD test t2 PRIMARY 1922, 1922