- 1 Performance Schema Quick Start
- 2 Performance Schema Configuration
- 3 Performance Schema Status Monitoring
- 4 Performance Schema Event Timing
- 5 Performance Schema Event Instrument Naming Conventions
- 6 Performance Schema Table General Characteristics
- 7 Performance Schema Table Descriptions
- 8 Performance Schema and Plugins
- 9 Performance Schema System Variables
- 10 Performance Schema Status Variables
- 11 Using Performance Schema to Diagnose Problems
- 12 Performance Schema Restrictions
- 13 Other Changes to Manual
The database name performance_schema is
lowercase. The names of tables in the database are uppercase.
Normal case sensitivity rules apply, so on systems with
case-sensitive file names, the database name and table names must
be specified in the lettercase just indicated. This behavior can
be modified by setting the
lower_case_table_names system
variable.
Most tables in the performance_schema database
are read only and cannot be modified. Some of the setup tables
have columns that can be modified to affect Performance Schema
operation. Truncation is allowed to clear collected events or
aggregation counters, so TRUNCATE
TABLE can be used on tables containing those kinds of
information, such as tables named with a prefix of
EVENTS_WAITS.
Privileges are as for other databases and tables:
To retrieve from
performance_schematables, you must have theSELECTprivilege.To change those columns that can be modified, you must have the
UPDATEprivilege.To truncate tables that can be truncated, you must have the
DROPprivilege.
