Rechercher dans le manuel MySQL
25.39.21 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.
This table is deprecated and is removed as of MySQL 8.0.1. Use
the Performance Schema
data_lock_waits table instead. See
Section 26.12.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 25.5 Mapping from INNODB_LOCK_WAITS to data_lock_waits Columns
| INNODB_LOCK_WAITS Column | data_lock_waits Column |
|---|---|
REQUESTING_TRX_ID |
REQUESTING_ENGINE_TRANSACTION_ID |
REQUESTED_LOCK_ID |
REQUESTING_ENGINE_LOCK_ID |
BLOCKING_TRX_ID |
BLOCKING_ENGINE_TRANSACTION_ID |
BLOCKING_LOCK_ID |
BLOCKING_ENGINE_LOCK_ID |
Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/mysql-rf-innodb-lock-waits-table.html
The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.
References
These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.
