PDF (A4) - 35.2Mb
Man Pages (TGZ) - 256.4Kb
Man Pages (Zip) - 361.2Kb
Info (Gzip) - 3.4Mb
Info (Zip) - 3.4Mb
MySQL Globalization
MySQL Information Schema
MySQL Installation Guide
MySQL and Linux/Unix
MySQL and macOS
MySQL Partitioning
MySQL Performance Schema
MySQL Replication
Using the MySQL Yum Repository
MySQL Restrictions and Limitations
Security in MySQL
MySQL and Solaris
Building MySQL from Source
Starting and Stopping MySQL
MySQL Tutorial
MySQL and Windows
MySQL NDB Cluster 7.5
The value of theshow_compatibility_56 system variable affects the information available from the tables described here. For details, see the description of that variable inSection 5.1.7, “Server System Variables”.
The Performance Schema makes status variable information available in the tables described inSection 25.12.14, “Performance Schema Status Variable Tables”. It also makes aggregated status variable information available in summary tables, described here. Each status variable summary table has one or more grouping columns to indicate how the table aggregates status values:
status_by_accounthasUSER,HOST, andVARIABLE_NAMEcolumns to summarize status variables by account.status_by_hosthasHOSTandVARIABLE_NAMEcolumns to summarize status variables by the host from which clients connected.status_by_userhasUSERandVARIABLE_NAMEcolumns to summarize status variables by client user name.
Each status variable summary table has this summary column containing aggregated values:
VARIABLE_VALUEThe aggregated status variable value for active and terminated sessions.
The meaning of“account” in these tables is similar to its meaning in the MySQL grant tables in themysql system database, in the sense that the term refers to a combination of user and host values. They differ in that, for grant tables, the host part of an account can be a pattern, whereas for Performance Schema tables, the host value is always a specific nonpattern host name.
Account status is collected when sessions terminate. The session status counters are added to the global status counters and the corresponding account status counters. If account statistics are not collected, the session status is added to host and user status, if host and user status are collected.
Account, host, and user statistics are not collected if theperformance_schema_accounts_size,performance_schema_hosts_size, andperformance_schema_users_size system variables, respectively, are set to 0.
The Performance Schema supportsTRUNCATE TABLE for status variable summary tables as follows; in all cases, status for active sessions is unaffected:
status_by_account: Aggregates account status from terminated sessions to user and host status, then resets account status.status_by_host: Resets aggregated host status from terminated sessions.status_by_user: Resets aggregated user status from terminated sessions.
FLUSH STATUS adds the session status from all active sessions to the global status variables, resets the status of all active sessions, and resets account, host, and user status values aggregated from disconnected sessions.
PDF (A4) - 35.2Mb
Man Pages (TGZ) - 256.4Kb
Man Pages (Zip) - 361.2Kb
Info (Gzip) - 3.4Mb
Info (Zip) - 3.4Mb
MySQL Globalization
MySQL Information Schema
MySQL Installation Guide
MySQL and Linux/Unix
MySQL and macOS
MySQL Partitioning
MySQL Performance Schema
MySQL Replication
Using the MySQL Yum Repository
MySQL Restrictions and Limitations
Security in MySQL
MySQL and Solaris
Building MySQL from Source
Starting and Stopping MySQL
MySQL Tutorial
MySQL and Windows
MySQL NDB Cluster 7.5