PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.1Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/parenthesized-query-expressions.html
parenthesized_query_expression: ( query_expression [order_by_clause] [limit_clause] ) [order_by_clause] [limit_clause] [into_clause] query_expression: query_block [set_op query_block [set_op query_block ...]] [order_by_clause] [limit_clause] ...
https://dev.mysql.com/doc/refman/8.0/en/partitioning-columns-range.html
Range columns partitioning is similar to range partitioning, but enables you to define partitions using ranges based on multiple column values. In addition, you can define the ranges using columns of types other than integer types. RANGE COLUMNS ...
https://dev.mysql.com/doc/refman/8.0/en/partitioning-info.html
This section discusses obtaining information about existing partitions, which can be done in a number of ways. Methods of obtaining such information include the following: Using the SHOW CREATE TABLE statement to view the partitioning clauses used ...
https://dev.mysql.com/doc/refman/8.0/en/partitioning-key.html
Partitioning by key is similar to partitioning by hash, except that where hash partitioning employs a user-defined expression, the hashing function for key partitioning is supplied by the MySQL server. NDB Cluster uses MD5() for this purpose; for ...
https://dev.mysql.com/doc/refman/8.0/en/partitioning-limitations-storage-engines.html
In MySQL 8.0, partitioning support is not actually provided by the MySQL Server, but rather by a table storage engine's own or native partitioning handler. In MySQL 8.0, only the InnoDB and NDB storage engines provide native partitioning handlers.
https://dev.mysql.com/doc/refman/8.0/en/partitioning-management-hash-key.html
Tables which are partitioned by hash or by key are very similar to one another with regard to making changes in a partitioning setup, and both differ in a number of ways from tables which have been partitioned by range or list. For that reason, ...
https://dev.mysql.com/doc/refman/8.0/en/partitioning-management-range-list.html
Adding and dropping of range and list partitions are handled in a similar fashion, so we discuss the management of both sorts of partitioning in this section. For information about working with tables that are partitioned by hash or key, see ...
https://dev.mysql.com/doc/refman/8.0/en/partitioning-overview.html
This section provides a conceptual overview of partitioning in MySQL 8.0. For information on partitioning restrictions and feature limitations, see Section 26.6, “Restrictions and Limitations on Partitioning”. The SQL standard does not provide ...
https://dev.mysql.com/doc/refman/8.0/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/8.0/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 ...