Documentation Home
MySQL 8.0 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 33.3Mb
PDF (A4) - 33.3Mb
PDF (RPM) - 31.3Mb
HTML Download (TGZ) - 7.9Mb
HTML Download (Zip) - 8.0Mb
HTML Download (RPM) - 6.8Mb
Man Pages (TGZ) - 144.9Kb
Man Pages (Zip) - 205.9Kb
Info (Gzip) - 3.0Mb
Info (Zip) - 3.0Mb


MySQL 8.0 Reference Manual  /  ...  /  The INFORMATION_SCHEMA INNODB_LOCK_WAITS Table

Pre-General Availability Draft: 2017-09-19

24.31.15 The INFORMATION_SCHEMA INNODB_LOCK_WAITS Table

The INNODB_LOCK_WAITS table contains one or more rows for each blocked InnoDB transaction, indicating the lock it has requested and any locks that are blocking that request.

Note

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

The tables differ in the privileges required: The INNODB_LOCK_WAITS table requires the global PROCESS privilege. The data_lock_waits table requires the usual Performance Schema privilege of SELECT on the table to be selected from.

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

Table 24.15 Mapping from INNODB_LOCK_WAITS to data_lock_waits Columns

INNODB_LOCK_WAITS Columndata_lock_waits Column
REQUESTING_TRX_IDREQUESTING_ENGINE_TRANSACTION_ID
REQUESTED_LOCK_IDREQUESTING_ENGINE_LOCK_ID
BLOCKING_TRX_IDBLOCKING_ENGINE_TRANSACTION_ID
BLOCKING_LOCK_IDBLOCKING_ENGINE_LOCK_ID


User Comments
Sign Up Login You must be logged in to post a comment.