- 22.9 Performance Schema Table Descriptions
- 22.9.1 Performance Schema Table Index
- 22.9.2 Performance Schema Setup Tables
- 22.9.3 Performance Schema Instance Tables
- 22.9.4 Performance Schema Wait Event Tables
- 22.9.5 Performance Schema Stage Event Tables
- 22.9.6 Performance Schema Statement Event Tables
- 22.9.7 Performance Schema Connection Tables
- 22.9.8 Performance Schema Connection Attribute Tables
- 22.9.9 Performance Schema Summary Tables
- 22.9.10 Performance Schema Miscellaneous Tables
[+/-]
Summary tables provide aggregated information for terminated events over time. The tables in this group summarize event data in different ways.
Event Wait Summaries:
events_waits_summary_global_by_event_name: Wait events summarized per event nameevents_waits_summary_by_instance: Wait events summarized per instanceevents_waits_summary_by_thread_by_event_name: Wait events summarized per thread and event name
Stage Summaries:
events_stages_summary_by_thread_by_event_name: Stage waits summarized per thread and event nameevents_stages_summary_global_by_event_name: Stage waits summarized per event name
Statement Summaries:
events_statements_summary_by_digest: Statement events summarized per schema and digest valueevents_statements_summary_by_thread_by_event_name: Statement events summarized per thread and event nameevents_statements_summary_global_by_event_name: Statement events summarized per event name
Object Wait Summaries:
objects_summary_global_by_type: Object summaries
File I/O Summaries:
file_summary_by_event_name: File events summarized per event namefile_summary_by_instance: File events summarized per file instance
Table I/O and Lock Wait Summaries:
table_io_waits_summary_by_index_usage: Table I/O waits per indextable_io_waits_summary_by_table: Table I/O waits per tabletable_lock_waits_summary_by_table: Table lock waits per table
Connection Summaries:
events_waits_summary_by_account_by_event_name: Wait events summarized per account and event nameevents_waits_summary_by_user_by_event_name: Wait events summarized per user name and event nameevents_waits_summary_by_host_by_event_name: Wait events summarized per host name and event nameevents_stages_summary_by_account_by_event_name: Stage events summarized per account and event nameevents_stages_summary_by_user_by_event_name: Stage events summarized per user name and event nameevents_stages_summary_by_host_by_event_name: Stage events summarized per host name and event nameevents_statements_summary_by_digest: Statement events summarized per schema and digest valueevents_statements_summary_by_account_by_event_name: Statement events summarized per account and event nameevents_statements_summary_by_user_by_event_name: Statement events summarized per user name and event nameevents_statements_summary_by_host_by_event_name: Statement events summarized per host name and event name
Socket Summaries:
socket_summary_by_instance: Socket waits and I/O summarized per instancesocket_summary_by_event_name: Socket waits and I/O summarized per event name
Each summary table has grouping columns that determine how to group the data to be aggregated, and summary columns that contain the aggregated values. Tables that summarize events in similar ways often have similar sets of summary columns and differ only in the grouping columns used to determine how events are aggregated.
Summary tables can be truncated with
TRUNCATE TABLE. Except for
events_statements_summary_by_digest,
the effect is to reset the summary columns to 0 or
NULL, not to remove rows. This enables you to
clear collected values and restart aggregation. That might be
useful, for example, after you have made a runtime configuration
change.
User Comments