contains current stage events, one row per thread showing the
current status of the thread's most recent monitored stage
Of the tables that contain stage event rows,
events_stages_current is the most
fundamental. Other tables that contain stage event rows are
logically derived from the current events. For example, the
are collections of the most recent stage events, up to a fixed
number of rows.
has these columns:
The thread associated with the event. 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.
The thread current event number when the event starts.
This column is set to
NULL when the
event starts, and updated to the thread current event
number when the event ends. This column was added in MySQL
The name of the instrument that produced the event. This
Instrument names have multiple parts and form a hierarchy,
as discussed in
Section 21.4, “Performance Schema Instrument Naming Conventions”.
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,
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 184.108.40.206, “Performance Schema Event Timing”.
EVENT_ID value of the event within
which this event is nested. The nesting event for a stage
event is usually a statement event.
The nesting event type. The value is
was added in MySQL 5.6.3.