INNODB_TRX table provides
information about every transaction (excluding read-only
transactions) currently executing inside
InnoDB, including whether the transaction is
waiting for a lock, when the transaction started, and the SQL
statement the transaction is executing, if any.
For usage information, see Section 220.127.116.11, “Using InnoDB Transaction and Locking Information”.
INNODB_TRX table has these
A unique transaction ID number, internal to
InnoDB. These IDs are not created for transactions that are read only and nonlocking. For details, see Section 8.5.3, “Optimizing InnoDB Read-Only Transactions”.
The weight of a transaction, reflecting (but not necessarily the exact count of) the number of rows altered and the number of rows locked by the transaction. To resolve a deadlock,
InnoDBselects the transaction with the smallest weight as the “victim” to roll back. Transactions that have changed nontransactional tables are considered heavier than others, regardless of the number of altered and locked rows.
The transaction execution state. Permitted values are
ROLLING BACK, and
The transaction start time.
The ID of the lock the transaction is currently waiting for, if
LOCK WAIT; otherwise
NULL. To obtain details about the lock, join this column with the
LOCK_IDcolumn of the
The time when the transaction started waiting on the lock, if
LOCK WAIT; otherwise
The MySQL thread ID. To obtain details about the thread, join this column with the
IDcolumn of the
PROCESSLISTtable, but see Section 18.104.22.168, “Persistence and Consistency of InnoDB Transaction and Locking Information”.
The SQL statement that is being executed by the transaction.
The transaction's current operation, if any; otherwise
The number of
InnoDBtables used while processing the current SQL statement of this transaction.
The number of
InnoDBtables that the current SQL statement has row locks on. (Because these are row locks, not table locks, the tables can usually still be read from and written to by multiple transactions, despite some rows being locked.)
The number of locks reserved by the transaction.
The total size taken up by the lock structures of this transaction in memory.
The approximate number or rows locked by this transaction. The value might include delete-marked rows that are physically present but not visible to the transaction.
The number of modified and inserted rows in this transaction.
A value indicating how much work the current transaction can do before being swapped out, as specified by the
The isolation level of the current transaction.
Whether unique checks are turned on or off for the current transaction. For example, they might be turned off during a bulk data load.
Whether foreign key checks are turned on or off for the current transaction. For example, they might be turned off during a bulk data load.
The detailed error message for the last foreign key error, if any; otherwise
Whether the adaptive hash index is locked by the current transaction. When the adaptive hash index search system is partitioned, a single transaction does not lock the entire adaptive hash index. Adaptive hash index partitioning is controlled by
innodb_adaptive_hash_index_parts, which is set to 8 by default.
Whether to relinquish the search latch immediately for the adaptive hash index, or reserve it across calls from MySQL. When there is no adaptive hash index contention, this value remains zero and statements reserve the latch until they finish. During times of contention, it counts down to zero, and statements release the latch immediately after each row lookup. When the adaptive hash index search system is partitioned (controlled by
innodb_adaptive_hash_index_parts), the value remains 0.
A value of 1 indicates the transaction is read only.
A value of 1 indicates the transaction is a
SELECTstatement that does not use the
LOCK IN SHARED MODEclauses, and is executing with
autocommitenabled so that the transaction will contain only this one statement. When this column and
TRX_IS_READ_ONLYare both 1,
InnoDBoptimizes the transaction to reduce the overhead associated with transactions that change table data.
mysql> SELECT * FROM INFORMATION_SCHEMA.INNODB_TRX\G *************************** 1. row *************************** trx_id: 1510 trx_state: RUNNING trx_started: 2014-11-19 13:24:40 trx_requested_lock_id: NULL trx_wait_started: NULL trx_weight: 586739 trx_mysql_thread_id: 2 trx_query: DELETE FROM employees.salaries WHERE salary > 65000 trx_operation_state: updating or deleting trx_tables_in_use: 1 trx_tables_locked: 1 trx_lock_structs: 3003 trx_lock_memory_bytes: 450768 trx_rows_locked: 1407513 trx_rows_modified: 583736 trx_concurrency_tickets: 0 trx_isolation_level: REPEATABLE READ trx_unique_checks: 1 trx_foreign_key_checks: 1 trx_last_foreign_key_error: NULL trx_adaptive_hash_latched: 0 trx_adaptive_hash_timeout: 10000 trx_is_read_only: 0 trx_autocommit_non_locking: 0
Use this table to help diagnose performance problems that occur during times of heavy concurrent load. Its contents are updated as described in Section 22.214.171.124, “Persistence and Consistency of InnoDB Transaction and Locking Information”.
You must have the
PROCESSprivilege to query this table.