Rechercher dans le manuel MySQL
26.12.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.
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 26.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 26.9, “Performance Schema Tables for Current and Historical Events”.
For information about configuring whether to collect stage events, see Section 26.12.5, “Performance Schema Stage Event Tables”.
Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/mysql-rf-events-stages-history-long-table.html
The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.
References
These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.
