# Performance Schema events\_transactions\_current Table
{% hint style="info" %}
The `events_transactions_current` table is available from MariaDB 10.5.2.
{% endhint %}
The `events_transactions_current` table contains current transaction events for each thread.
The table size cannot be figured, and always stores one row for each thread, showing the current status of the thread's most recent monitored transaction event.
The table contains the following columns:
| Column | Type | Description |
| ----------------------------------- | ------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| THREAD\_ID | bigint(20) unsigned | The thread associated with the event. |
| EVENT\_ID | bigint(20) unsigned | The event id associated with the event. |
| END\_EVENT\_ID | bigint(20) unsigned | This column is set to NULL when the event starts and updated to the thread current event number when the event ends. |
| EVENT\_NAME | varchar(128) | The name of the instrument from which the event was collected. This is a NAME value from the setup\_instruments table. |
| STATE | enum('ACTIVE', 'COMMITTED', 'ROLLED BACK') | The current transaction state. The value is ACTIVE (after START TRANSACTION or BEGIN), COMMITTED (after COMMIT), or ROLLED BACK (after ROLLBACK). |
| TRX\_ID | bigint(20) unsigned | Unused. |
| GTID | varchar(64) | Transaction [GTID](/docs/server/ha-and-performance/standard-replication/gtid.md), using the format DOMAIN-SERVER\_ID-SEQUENCE\_NO. |
| XID\_FORMAT\_ID | int(11) | XA transaction format ID for GTRID and BQUAL values. |
| XID\_GTRID | varchar(130) | XA global transaction ID. |
| XID\_BQUAL | varchar(130) | XA transaction branch qualifier. |
| XA\_STATE | varchar(64) | 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). |
| SOURCE | varchar(64) | 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. |
| TIMER\_START | bigint(20) unsigned | The unit is picoseconds. When event timing started. NULL if event has no timing information. |
| TIMER\_END | bigint(20) unsigned | The unit is picoseconds. When event timing ended. NULL if event has no timing information. |
| TIMER\_WAIT | bigint(20) unsigned | The unit is picoseconds. Event duration. NULL if event has not timing information. |
| ACCESS\_MODE | enum('READ ONLY', 'READ WRITE') | Transaction access mode. |
| ISOLATION\_LEVEL | varchar(64) | Transaction isolation level. One of: REPEATABLE READ, READ COMMITTED, READ UNCOMMITTED, or SERIALIZABLE. |
| AUTOCOMMIT | enum('YES','NO') | Whether autcommit mode was enabled when the transaction started. |
| NUMBER\_OF\_SAVEPOINTS | bigint(20) unsigned | The number of SAVEPOINT statements issued during the transaction. |
| NUMBER\_OF\_ROLLBACK\_TO\_SAVEPOINT | bigint(20) unsigned | The number of ROLLBACK\_TO\_SAVEPOINT statements issued during the transaction. |
| NUMBER\_OF\_RELEASE\_SAVEPOINT | bigint(20) unsigned | The number of RELEASE\_SAVEPOINT statements issued during the transaction. |
| OBJECT\_INSTANCE\_BEGIN | bigint(20) unsigned | Unused. |
| NESTING\_EVENT\_ID | bigint(20) unsigned | The EVENT\_ID value of the event within which this event is nested. |
| NESTING\_EVENT\_TYPE | enum('TRANSACTION', 'STATEMENT', 'STAGE', 'WAIT') | The nesting event type. |
*This page is licensed: CC BY-SA / Gnu FDL*
{% @marketo/form formId="4316" %}
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://mariadb.com/docs/server/reference/system-tables/performance-schema/performance-schema-tables/performance-schema-events_transactions_current-table.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.