Table of Contents
- 10.1 Performance Schema Table Reference
- 10.2 Performance Schema Setup Tables
- 10.3 Performance Schema Instance Tables
- 10.4 Performance Schema Wait Event Tables
- 10.5 Performance Schema Stage Event Tables
- 10.6 Performance Schema Statement Event Tables
- 10.7 Performance Schema Transaction Tables
- 10.8 Performance Schema Connection Tables
- 10.9 Performance Schema Connection Attribute Tables
- 10.10 Performance Schema User-Defined Variable Tables
- 10.11 Performance Schema Replication Tables
- 10.11.1 The replication_connection_configuration Table
- 10.11.2 The replication_connection_status Table
- 10.11.3 The replication_applier_configuration Table
- 10.11.4 The replication_applier_status Table
- 10.11.5 The replication_applier_status_by_coordinator Table
- 10.11.6 The replication_applier_status_by_worker Table
- 10.11.7 The replication_group_members Table
- 10.11.8 The replication_group_member_stats Table
- 10.12 Performance Schema Lock Tables
- 10.13 Performance Schema System Variable Tables
- 10.14 Performance Schema Status Variable Tables
- 10.15 Performance Schema Summary Tables
- 10.15.1 Wait Event Summary Tables
- 10.15.2 Stage Summary Tables
- 10.15.3 Statement Summary Tables
- 10.15.4 Transaction Summary Tables
- 10.15.5 Object Wait Summary Table
- 10.15.6 File I/O Summary Tables
- 10.15.7 Table I/O and Lock Wait Summary Tables
- 10.15.8 Socket Summary Tables
- 10.15.9 Memory Summary Tables
- 10.15.10 Status Variable Summary Tables
- 10.16 Performance Schema Miscellaneous Tables
Tables in the
performance_schema database can
be grouped as follows:
Setup tables. These tables are used to configure and display monitoring characteristics.
Current events tables. The
events_waits_currenttable contains the most recent event for each thread. Other similar tables contain current events at different levels of the event hierarchy:
events_stages_currentfor stage events,
events_statements_currentfor statement events, and
events_transactions_currentfor transaction events.
History tables. These tables have the same structure as the current events tables, but contain more rows. For example, for wait events,
events_waits_historytable contains the most recent 10 events per thread.
events_waits_history_longcontains the most recent 10,000 events. Other similar tables exist for stage, statement, and transaction histories.
To change the sizes of the history tables, set the appropriate system variables at server startup. For example, to set the sizes of the wait event history tables, set
Summary tables. These tables contain information aggregated over groups of events, including those that have been discarded from the history tables.
Instance tables. These tables document what types of objects are instrumented. An instrumented object, when used by the server, produces an event. These tables provide event names and explanatory notes or status information.
Miscellaneous tables. These do not fall into any of the other table groups.