Documentation Home
MySQL Performance Schema
Related Documentation Download this Excerpt
PDF (US Ltr) - 1.0Mb
PDF (A4) - 1.0Mb
HTML Download (TGZ) - 158.6Kb
HTML Download (Zip) - 177.0Kb


10.5.3 The events_stages_history_long Table

The events_stages_history_long table contains the most recent N stage events. The value of N is autosized at server startup. To set the table size explicitly, set the performance_schema_events_stages_history_long_size system variable at server startup. Stage events are not added to the table until they have ended. As new events are added, older events are discarded if the table is full. When a thread ends, its rows are removed from the table.

The events_stages_history_long table has the same structure as events_stages_current, except that it has no indexes. 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 information about configuration of stage event collection, 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.