content_image/830368.jpg
## Notes 

INDEX_ID: 40 NAME: i1 TABLE_ID: 34 TYPE: 0 N_FIELDS: 1 PAGE_NO: 4 SPACE: 23 MERGE_THRESHOLD: 50 

•You must have the PROCESS  privilege to query this table. 

•Use the INFORMATION_SCHEMA COLUMNS  table or the SHOW COLUMNS  statement to view additional information about the columns of this table, including data types and default values. 

## 26.4.21 The INFORMATION_SCHEMA INNODB_LOCKS Table 

The INNODB_LOCKS  table provides information about each lock that an InnoDB  transaction has requested but not yet acquired, and each lock that a transaction holds that is blocking another transaction. 

## Note 

This table is deprecated and is removed as of MySQL 8.0.1. Use the Performance Schema data_locks  table instead. See Section 27.12.13.1, “The data_locks Table” . 

Differences between INNODB_LOCKS  and data_locks : 

•If a transaction holds a lock, INNODB_LOCKS  displays the lock only if another transaction is waiting for it. data_locks  displays the lock regardless of whether any transaction is waiting for it. 

•The data_locks  table has no columns corresponding to LOCK_SPACE , LOCK_PAGE , or LOCK_REC . 

•The INNODB_LOCKS  table requires the global PROCESS  privilege. The data_locks  table requires the usual Performance Schema privilege of SELECT on the table to be selected from. 

The following table shows the mapping from INNODB_LOCKS  columns to data_locks  columns. Use this information to migrate applications from one table to the other. 

<img src='content_image/830368.jpg'>

