MySQL 8.0 Reference Manual Including MySQL NDB Cluster 8.0
Summary tables provide aggregated information for terminated events over time. The tables in this group summarize event data in different ways.
events_waits_summary_by_account_by_event_name
:
Wait events per account and event name
events_waits_summary_by_host_by_event_name
:
Wait events per host name and event name
events_waits_summary_by_instance
:
Wait events per instance
events_waits_summary_by_thread_by_event_name
:
Wait events per thread and event name
events_waits_summary_by_user_by_event_name
:
Wait events per user name and event name
events_waits_summary_global_by_event_name
:
Wait events per event name
events_stages_summary_by_account_by_event_name
:
Stage events per account and event name
events_stages_summary_by_host_by_event_name
:
Stage events per host name and event name
events_stages_summary_by_thread_by_event_name
:
Stage waits per thread and event name
events_stages_summary_by_user_by_event_name
:
Stage events per user name and event name
events_stages_summary_global_by_event_name
:
Stage waits per event name
events_statements_histogram_by_digest
:
Statement histograms per schema and digest value.
events_statements_histogram_global
:
Statement histogram summarized globally.
events_statements_summary_by_account_by_event_name
:
Statement events per account and event name
events_statements_summary_by_digest
:
Statement events per schema and digest value
events_statements_summary_by_host_by_event_name
:
Statement events per host name and event name
events_statements_summary_by_program
:
Statement events per stored program (stored procedures and
functions, triggers, and events)
events_statements_summary_by_thread_by_event_name
:
Statement events per thread and event name
events_statements_summary_by_user_by_event_name
:
Statement events per user name and event name
events_statements_summary_global_by_event_name
:
Statement events per event name
prepared_statements_instances
:
Prepared statement instances and statistics
events_transactions_summary_by_account_by_event_name
:
Transaction events per account and event name
events_transactions_summary_by_host_by_event_name
:
Transaction events per host name and event name
events_transactions_summary_by_thread_by_event_name
:
Transaction events per thread and event name
events_transactions_summary_by_user_by_event_name
:
Transaction events per user name and event name
events_transactions_summary_global_by_event_name
:
Transaction events per event name
objects_summary_global_by_type
:
Object summaries
file_summary_by_event_name
:
File events per event name
file_summary_by_instance
: File
events per file instance
table_io_waits_summary_by_index_usage
:
Table I/O waits per index
table_io_waits_summary_by_table
:
Table I/O waits per table
table_lock_waits_summary_by_table
:
Table lock waits per table
socket_summary_by_instance
:
Socket waits and I/O per instance
socket_summary_by_event_name
:
Socket waits and I/O per event name
memory_summary_by_account_by_event_name
:
Memory operations per account and event name
memory_summary_by_host_by_event_name
:
Memory operations per host and event name
memory_summary_by_thread_by_event_name
:
Memory operations per thread and event name
memory_summary_by_user_by_event_name
:
Memory operations per user and event name
memory_summary_global_by_event_name
:
Memory operations globally per event name
events_errors_summary_by_account_by_error
:
Errors per error code and account
events_errors_summary_by_host_by_error
:
Errors per error code and host
events_errors_summary_by_thread_by_error
:
Errors per error code and thread
events_errors_summary_by_user_by_error
:
Errors per error code and user
events_errors_summary_global_by_error
:
Errors per error code
status_by_account
: Status
variables per account
status_by_host
: Status
variables per host name
status_by_user
: Status
variables per user 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
. Generally, 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. Exceptions to this truncation behavior are noted in
individual summary table sections.