PDF (US Ltr)
- 41.9Mb
PDF (A4)
- 42.0Mb
Man Pages (TGZ)
- 272.3Kb
Man Pages (Zip)
- 378.3Kb
Info (Gzip)
- 4.2Mb
Info (Zip)
- 4.2Mb
Search Results
https://dev.mysql.com/doc/refman/9.7/en/partitioning-pruning.html
The optimization known as partition pruning is based on a relatively simple concept which can be described as “Do not scan partitions where there can be no matching values”. By limiting the search, it is possible to expend much less time and ...
https://dev.mysql.com/doc/refman/9.7/en/performance-schema-consumer-configurations.html
The consumer settings in the setup_consumers table form a hierarchy from higher levels to lower. The following discussion describes how consumers work, showing specific configurations and their effects as consumer settings are enabled progressively ...
https://dev.mysql.com/doc/refman/9.7/en/performance-schema-event-tables.html
For wait, stage, statement, and transaction events, the Performance Schema can monitor and store current events. In addition, when events end, the Performance Schema can store them in history tables. For each event type, the Performance Schema uses ...
https://dev.mysql.com/doc/refman/9.7/en/performance-schema-firewall-tables.html
The following sections describe the Performance Schema tables associated with MySQL Enterprise Firewall (see Section 8.4.9, “MySQL Enterprise Firewall”). They provide information about firewall operation: firewall_groups: Information about ...
https://dev.mysql.com/doc/refman/9.7/en/performance-schema-instrument-naming.html
An instrument name consists of a sequence of elements separated by '/' characters. Example names: wait/io/file/myisam/log wait/io/file/mysys/charset wait/lock/table/sql/handler wait/synch/cond/mysys/COND_alarm ...
https://dev.mysql.com/doc/refman/9.7/en/performance-schema-mutex-instances-table.html
The mutex_instances table lists all the mutexes seen by the Performance Schema while the server executes. A mutex is a synchronization mechanism used in the code to enforce that only one thread at a given time can have access to some common ...
https://dev.mysql.com/doc/refman/9.7/en/performance-schema-queries.html
Pre-filtering limits which event information is collected and is independent of any particular user. By contrast, post-filtering is performed by individual users through the use of queries with appropriate WHERE clauses that restrict what event ...
https://dev.mysql.com/doc/refman/9.7/en/performance-schema-quick-start.html
This section briefly introduces the Performance Schema with examples that show how to use it. For additional examples, see Section 29.19, “Using the Performance Schema to Diagnose Problems”. To enable or disable it explicitly, start the server ...
https://dev.mysql.com/doc/refman/9.7/en/performance-schema-replication-tables.html
This is similar to the information available from the SHOW REPLICA STATUS statement, but representation in table form is more accessible and has usability benefits: SHOW REPLICA STATUS output is useful for visual inspection, but not so much for ...
https://dev.mysql.com/doc/refman/9.7/en/performance-schema-rwlock-instances-table.html
The rwlock_instances table lists all the rwlock (read write lock) instances seen by the Performance Schema while the server executes. An rwlock is a synchronization mechanism used in the code to enforce that threads at a given time can have access ...