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/partitioning-limitations-functions.html
This section discusses limitations in MySQL Partitioning relating specifically to functions used in partitioning expressions. Each of these functions returns an integer only if it is passed an argument of an exact numeric type, such as one of the ...
https://dev.mysql.com/doc/refman/5.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/5.7/en/performance-schema-events-transactions-current-table.html
The table stores one row per thread showing the current status of the thread's most recent monitored transaction event, so there is no system variable for configuring the table size. For example: mysql> SELECT * FROM ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-file-instances-table.html
The file_instances table lists all the files seen by the Performance Schema when executing file I/O instrumentation. If a file on disk has never been opened, it is not in file_instances. When a file is deleted from the disk, it is also removed from ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-filtering.html
Events are processed in a producer/consumer fashion: Instrumented code is the source for events and produces events to be collected. The setup_instruments table lists the instruments for which events can be collected, whether they are enabled, and ...
https://dev.mysql.com/doc/refman/5.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/5.7/en/performance-schema-replication-applier-status-by-worker-table.html
If the replica is not multithreaded, this table shows the status of the applier thread. Otherwise, the replica uses multiple worker threads and a coordinator thread to manage them, and this table shows the status of the worker threads. For a ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-replication-connection-configuration-table.html
This table shows the configuration parameters used by the replica for connecting to the source. Parameters stored in the table can be changed at runtime with the CHANGE MASTER TO statement, as indicated in the column descriptions. It contains ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-startup-configuration.html
To use the MySQL Performance Schema, it must be enabled at server startup to enable event collection to occur. Assuming that the Performance Schema is available, it is enabled by default. To enable or disable it explicitly, start the server with ...
https://dev.mysql.com/doc/refman/5.7/en/performance-schema-wait-tables.html
The Performance Schema instruments waits, which are events that take time. Within the event hierarchy, wait events nest within stage events, which nest within statement events, which nest within transaction events. These tables store wait events: ...