MySQL uses metadata locking to manage concurrent access to
database objects and to ensure data consistency; see
Section 8.11.4, “Metadata Locking”. Metadata locking applies
not just to tables, but also to schemas, stored programs
(procedures, functions, triggers, scheduled events),
tablespaces, user locks acquired with the
GET_LOCK() function (see
Section 12.14, “Locking Functions”), and locks acquired with
the locking service described in
Section 29.3.1, “The Locking Service”.
The Performance Schema exposes metadata lock information
Locks that have been granted (shows which sessions own which current metadata locks).
Locks that have been requested but not yet granted (shows which sessions are waiting for which metadata locks).
Lock requests that have been killed by the deadlock detector.
Lock requests that have timed out and are waiting for the requesting session's lock request to be discarded.
This information enables you to understand metadata lock dependencies between sessions. You can see not only which lock a session is waiting for, but which session currently holds that lock.
Metadata lock instrumentation uses the
which is enabled by default.
To control metadata lock instrumentation state at server
startup, use lines like these in your
To control metadata lock instrumentation state at runtime,
UPDATE performance_schema.setup_instruments SET ENABLED = 'YES', TIMED = 'YES' WHERE NAME = 'wait/lock/metadata/sql/mdl';
UPDATE performance_schema.setup_instruments SET ENABLED = 'NO', TIMED = 'NO' WHERE NAME = 'wait/lock/metadata/sql/mdl';
The Performance Schema maintains
metadata_locks table content as
follows, using the
LOCK_STATUS column to
indicate the status of each lock:
When a metadata lock is requested and obtained immediately, a row with a status of
When a metadata lock is requested and not obtained immediately, a row with a status of
When a metadata lock previously requested is granted, its row status is updated to
When a metadata lock is released, its row is deleted.
When a pending lock request is canceled by the deadlock detector to break a deadlock (
ER_LOCK_DEADLOCK), its row status is updated from
When a pending lock request times out (
ER_LOCK_WAIT_TIMEOUT), its row status is updated from
When granted lock or pending lock request is killed, its row status is updated from
KILLEDstatus values are brief and signify that the lock row is about to be deleted.
POST_RELEASE_NOTIFYstatus values are brief and signify that the metadata locking subsubsystem is notifying interested storage engines while entering lock acquisition operations or leaving lock release operations.
metadata_locks table has
The type of lock used in the metadata lock subsystem. The value is one of
USER LEVEL LOCK,
The schema that contains the object.
The name of the instrumented object.
The address in memory of the instrumented object.
The lock type from the metadata lock subsystem. The value is one of
The lock duration from the metadata lock subsystem. The value is one of
TRANSACTIONvalues signify locks that are released implicitly at statement or transaction end, respectively. The
EXPLICITvalue signifies locks that survive statement or transaction end and are released by explicit action, such as global locks acquired with
FLUSH TABLES WITH READ LOCK.
The lock status from the metadata lock subsystem. The value is one of
POST_RELEASE_NOTIFY. The Performance Schema assigns these values as described previously.
The name of the source file containing the instrumented code that produced the event and the line number in the file at which the instrumentation occurs. This enables you to check the source to determine exactly what code is involved.
The thread requesting a metadata lock.
The event requesting a metadata lock.
metadata_locks table has
Primary key on (
Index on (
Index on (