PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-instance-tables.html
Instrument names may have multiple parts and form a hierarchy, as discussed in Section 25.6, “Performance Schema Instrument Naming Conventions”. For examples of how to use them for this purpose, see Section 25.19, “Using the Performance Schema ...They provide event names and explanatory notes or status information: cond_instances: Condition synchronization object instances file_instances: File instances mutex_instances: Mutex synchronization object instances rwlock_instances: Lock synchronization object instances socket_instances: Active connection instances These tables list instrumented synchronization objects, files, and ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-query-profiling.html
The following example demonstrates how to use Performance Schema statement events and stage events to retrieve data comparable to profiling information provided by SHOW PROFILES and SHOW PROFILE statements. Performance Schema displays event timer ...The setup_actors table can be used to limit the collection of historical events by host, user, or account to reduce runtime overhead and the amount of data collected in history ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-restrictions.html
The Performance Schema avoids using mutexes to collect or produce data, so there are no guarantees of consistency and results can sometimes be incorrect. For example, if you select events from a performance_schema table into a temporary table, ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-table-characteristics.html
The name of the performance_schema database is lowercase, as are the names of tables within it. Many tables in the performance_schema database are read only and cannot be modified: mysql> TRUNCATE TABLE performance_schema.setup_instruments; ERROR ...Truncation is permitted to clear collected events, so TRUNCATE TABLE can be used on tables containing those kinds of information, such as tables named with a prefix of ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-replication-schema.html
Note When performing schema changes on NDB tables, applications should wait until the ALTER TABLE statement has returned in the MySQL client connection that issued the statement before attempting to use the updated definition of the table.
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-and-plugins.html
The associated event information, including aggregate information, remains readable in performance_schema database tables. For additional information about the effect of plugin installation and removal, see Section 25.7, “Performance Schema Status ... Removing a plugin with UNINSTALL PLUGIN does not affect information already collected for code in that ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-lock-tables.html
The Performance Schema exposes lock information through these tables: metadata_locks: Metadata locks held and requested table_handles: Table locks held and requested The following sections describe these tables in more detail.
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-setup-tables.html
The use of tables rather than individual variables for setup information provides a high degree of flexibility in modifying Performance Schema configuration. The setup tables provide information about the current instrumentation and enable the ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-user-variable-tables.html
The Performance Schema provides a user_variables_by_thread table that exposes user-defined variables. These are variables defined within a specific session and include a @ character preceding the name; see Section 9.4, “User-Defined Variables”.
https://dev.mysql.com/doc/refman/5.7/en/sys-schema-functions.html
The following sections describe sys schema stored functions. ...