•Scheduled Events 

The execution of the statements in the body of a scheduled event takes place in a new connection. Nesting of a scheduled event within a parent transaction is not applicable. 

## Transactions and Savepoints 

Savepoint statements are recorded as separate statement events. Transaction events include separate counters for SAVEPOINT , ROLLBACK TO SAVEPOINT , and RELEASE SAVEPOINT  statements issued during the transaction. 

## Transactions and Errors 

Errors and warnings that occur within a transaction are recorded in statement events, but not in the corresponding transaction event. This includes transaction-specific errors and warnings, such as a rollback on a nontransactional table or GTID consistency errors. 

## 27.12.7.1 The events_transactions_current Table 

The events_transactions_current  table contains current transaction events. The table stores one row per thread showing the current status of the thread’s most recent monitored transaction event, so there is no system variable for configuring the table size. For example: 

mysql> SELECT * FROM performance_schema.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, 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 that have ended, up to a maximum number of rows per thread and globally across all threads, respectively. 

For more information about the relationship between the three transaction event tables, see Section 27.9, “Performance Schema Tables for Current and Historical Events” . 

For information about configuring whether to collect transaction events, see Section 27.12.7, “Performance Schema Transaction Tables” . 

