MySQL 9.1 Release Notes
The events_stages_history_long
table contains the N most recent
stage events that have ended globally, across all threads.
Stage events are not added to the table until they have ended.
When the table becomes full, the oldest row is discarded when
a new row is added, regardless of which thread generated
either row.
The Performance Schema autosizes the value of
N during server startup. To set the
table size explicitly, set the
performance_schema_events_stages_history_long_size
system variable at server startup.
The events_stages_history_long
table has the same columns as
events_stages_current. See
Section 29.12.5.1, “The events_stages_current Table”.
Unlike events_stages_current,
events_stages_history_long has no
indexing.
TRUNCATE TABLE is permitted for
the events_stages_history_long
table. It removes the rows.
For more information about the relationship between the three stage event tables, see Section 29.9, “Performance Schema Tables for Current and Historical Events”.
For information about configuring whether to collect stage events, see Section 29.12.5, “Performance Schema Stage Event Tables”.