Documentation Home
MySQL Performance Schema
Related Documentation Download this Excerpt
PDF (US Ltr) - 0.6Mb
PDF (A4) - 0.6Mb
HTML Download (TGZ) - 101.7Kb
HTML Download (Zip) - 119.9Kb


10.5.3 The events_stages_history_long Table

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. When a thread ends, all its rows are discarded.

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 10.5.1, “The events_stages_current Table”.

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 Performance Schema Tables for Current and Historical Events.

For information about configuring whether to collect stage events, see Section 10.5, “Performance Schema Stage Event Tables”.


User Comments
User comments in this section are, as the name implies, provided by MySQL users. The MySQL documentation team is not responsible for, nor do they endorse, any of the information provided here.
Sign Up Login You must be logged in to post a comment.