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:
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 SOURCE: transaction.cc:150 TIMER_START: 420833537900000 TIMER_END: NULL TIMER_WAIT: NULL ACCESS_MODE: READ WRITE ISOLATION_LEVEL: REPEATABLE READ AUTOCOMMIT: NO NUMBER_OF_SAVEPOINTS: 0 NUMBER_OF_ROLLBACK_TO_SAVEPOINT: 0 NUMBER_OF_RELEASE_SAVEPOINT: 0 OBJECT_INSTANCE_BEGIN: NULL NESTING_EVENT_ID: 6 NESTING_EVENT_TYPE: STATEMENT
Of the tables that contain transaction event rows,
the most fundamental. Other tables that contain transaction
event rows are logically derived from the current events. For
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”.
table has these columns:
The thread associated with the event and the thread
current event number when the event starts. The
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
Instrument names may have multiple parts and form a
hierarchy, as discussed in
Section 21.4, “Performance Schema Instrument Naming Conventions”.
This column changed in MySQL 5.7.6.
Versions of MySQL prior to 5.7.6:
gtid_mode=ON, this is
the value of
gtid_next when the
transaction started. If
the value is
the value is a GTID in
Versions of MySQL 5.7.6 and later:
The GTID column contains the value of
gtid_next, which can
be one of
AUTOMATIC, or a GTID using the
transactions that use
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_PERMISSIVE, the GTID column
changes to the transaction's GTID. If
gtid_mode is either
OFF_PERMISSIVE, the GTID column
The XA transaction identifier. It has the format described
in Section 220.127.116.11, “XA Transaction SQL Syntax”. This column was
removed in MySQL 5.7.7 and replaced with the
XID_BQUAL columns representing the
components of XID values.
The components of the XA transaction identifier. They have
the format described in Section 18.104.22.168, “XA Transaction SQL Syntax”.
These columns were added in MySQL 5.7.7 as replacements
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_END values indicate when event
timing started and ended.
the event elapsed time (duration).
If an event has not finished,
NULL before MySQL 5.7.8. As of 5.7.8,
TIMER_END is the current timer value
TIMER_WAIT is the time elapsed so
If an event is produced from an instrument that has
TIMED = NO, timing information is not
TIMER_WAIT are all
For discussion of picoseconds as the unit for event times and factors that affect time values, see Section 22.214.171.124, “Performance Schema Event Timing”.
The transaction access mode. The value is
The transaction isolation level. The value is
Whether autcommit mode was enabled when the transaction started.
EVENT_ID value of the event within
which this event is nested.
The nesting event type. The value is
will not appear because transactions cannot be nested.)