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.6.2 The events_statements_history Table

The events_statements_history table contains the N most recent statement events that have ended per thread. Statement events are not added to the table until they have ended. When the table contains the maximum number of rows for a given thread, the oldest thread row is discarded when a new row for that thread is added. When a thread ends, all its rows are discarded.

The Performance Schema autosizes the value of N during server startup. To set the number of rows per thread explicitly, set the performance_schema_events_statements_history_size system variable at server startup.

The events_statements_history table has the same columns as events_statements_current. See Section 10.6.1, “The events_statements_current Table”.

TRUNCATE TABLE is permitted for the events_statements_history table. It removes the rows.

For more information about the relationship between the three events_statements_xxx event tables, see Performance Schema Tables for Current and Historical Events.

For information about configuring whether to collect statement events, see Section 10.6, “Performance Schema Statement 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.