Documentation Home
MySQL 5.7 Reference Manual
Related Documentation Download this Manual Excerpts from this Manual The events_transactions_current Table

The events_transactions_current table (added in MySQL 5.7.3) contains current transaction events, one row per thread showing the current status of the thread's most recent monitored transaction event. For example:

mysql> SELECT * FROM events_transactions_current LIMIT 1\G
*************************** 1. row ***************************
                      THREAD_ID: 26
                       EVENT_ID: 7
                   END_EVENT_ID: NULL
                     EVENT_NAME: transaction
                          STATE: ACTIVE
                         TRX_ID: NULL
                           GTID: 3E11FA47-71CA-11E1-9E33-C80AA9429562:56
                            XID: NULL
                       XA_STATE: NULL
                    TIMER_START: 420833537900000
                      TIMER_END: NULL
                     TIMER_WAIT: NULL
                    ACCESS_MODE: READ WRITE
                     AUTOCOMMIT: NO
               NESTING_EVENT_ID: 6

The events_transactions_current table can be truncated with TRUNCATE TABLE.

Of the tables that contain transaction event rows, events_transactions_current is the most fundamental. Other tables that contain transaction event rows are logically derived from the current events. For example, the events_transactions_history and events_transactions_history_long tables are collections of the most recent transaction events, up to a fixed number of rows.

For information about configuration of transaction event collection, see Section 21.9.7, “Performance Schema Transaction Tables”.

The events_transactions_current table has these columns:


    The thread associated with the event and the thread current event number when the event starts. The THREAD_ID and EVENT_ID values taken together form a primary key that uniquely identifies the row. No two rows will have the same pair of values.


    This column is set to NULL when the event starts and updated to the thread current event number when the event ends.


    The name of the instrument from which the event was collected. This is a NAME value from the setup_instruments table. Instrument names may have multiple parts and form a hierarchy, as discussed in Section 21.4, “Performance Schema Instrument Naming Conventions”.


    The current transaction state. The value is ACTIVE (after START TRANSACTION or BEGIN), COMMITTED (after COMMIT), or ROLLED BACK (after ROLLBACK).

  • TRX_ID


  • GTID

    This column changed in MySQL 5.7.6.

    • Versions of MySQL prior to 5.7.6:

      If gtid_mode=OFF, the value is NULL. If gtid_mode=ON, this is the value of gtid_next when the transaction started. If gtid_next=AUTOMATIC the value is AUTOMATIC, otherwise the value is a GTID in UUID:NUMBER format.

    • Versions of MySQL 5.7.6 and later:

      The GTID column contains the value of gtid_next, which can be one of ANONYMOUS, AUTOMATIC, or a GTID using the format UUID:NUMBER. For transactions that use gtid_next=AUTOMATIC, which is all normal client transactions, the GTID column changes when the transaction commits and the actual GTID is assigned. If gtid_mode is either ON or ON_PERMISSIVE, the GTID column changes to the transaction's GTID. If gtid_mode is either OFF or OFF_PERMISSIVE, the GTID column changes to ANONYMOUS.

  • XID

    The XA transaction identifier. It has the format described in Section, “XA Transaction SQL Syntax”. This column was removed in MySQL 5.7.7 and replaced with the XID_FORMAT_ID, XID_GTRID, and XID_BQUAL columns representing the components of XID values.


    The components of the XA transaction identifier. They have the format described in Section, “XA Transaction SQL Syntax”. These columns were added in MySQL 5.7.7 as replacements for the XID column.


    The state of the XA transaction. The value is ACTIVE (after XA START), IDLE (after XA END), PREPARED (after XA PREPARE), ROLLED BACK (after XA ROLLBACK), or COMMITTED (after XA COMMIT).


    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.


    Timing information for the event. The unit for these values is picoseconds (trillionths of a second). The TIMER_START and TIMER_END values indicate when event timing started and ended. TIMER_WAIT is the event elapsed time (duration).

    If an event has not finished, TIMER_END and TIMER_WAIT are NULL before MySQL 5.7.8. As of 5.7.8, TIMER_END is the current timer value and TIMER_WAIT is the time elapsed so far (TIMER_ENDTIMER_START).

    If an event is produced from an instrument that has TIMED = NO, timing information is not collected, and TIMER_START, TIMER_END, and TIMER_WAIT are all NULL.

    For discussion of picoseconds as the unit for event times and factors that affect time values, see Section, “Performance Schema Event Timing”.


    The transaction access mode. The value is READ ONLY or READ WRITE.


    The transaction isolation level. The value is REPEATABLE READ, READ COMMITTED, READ UNCOMMITTED, or SERIALIZABLE.


    Whether autcommit mode was enabled when the transaction started.


    The number of SAVEPOINT, ROLLBACK TO SAVEPOINT, and RELEASE SAVEPOINT statements issued during the transaction.




    The EVENT_ID value of the event within which this event is nested.


    The nesting event type. The value is TRANSACTION, STATEMENT, STAGE, or WAIT. (TRANSACTION will not appear because transactions cannot be nested.)

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