Performance Schema events_waits_history_long Table
You are viewing an old version of this article. View the current version here.
events_waits_history_long table by default contains the ten thousand most recent completed wait events. This number can be adjusted by setting the performance_schema_events_waits_history_long_size system variable when the server starts up.
The table structure is identical to the events_waits_current table structure, and contains the following columns:
|Thread associated with the event. Together with |
|Thread's current event number at the start of the event. Together with|
|Event instrument name and a NAME from the |
|Name and line number of the source file containing the instrumented code that produced the event.|
|Value in picoseconds when the event timing started or |
|Value in picoseconds when the event timing ended, or |
|Value in picoseconds of the event's duration or |
|Number of spin rounds for a mutex, or |
|Name of the schema that contains the table for table I/O objects, otherwise |
|File name for file I/O objects, table name for table I/O objects, the socket's IP:PORT value for a socket object or |
|Name of the index, PRIMARY for the primary key, or |
|FILE for a file object, |
|Address in memory of the object.|
|Nesting event type. Either |
|Operation type, for example read, write or lock|
|Number of bytes that the operation read or wrote, or |
|Reserved for use in the future.|
It is possible to empty this table with a
TRUNCATE TABLE statement.
events_waits_current and events_waits_history are related tables.
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.