No cache version.
Caching disabled. Default setting for this page:enabled (code DEF204)If the display is too slow, you can disable the user mode to view the cached version.
Rechercher dans le manuel MySQL
Chapter 23 Partitioning
Table of Contents [+/-]
This chapter discusses user-defined partitioning.
Table partitioning differs from partitioning as used by window functions. For information about window functions, see Section 12.21, “Window Functions”.
In MySQL 8.0, partitioning support is provided by the
InnoDB and
NDB storage engines.
MySQL 8.0 does not currently support partitioning of
tables using any storage engine other than InnoDB
or NDB, such as
MyISAM. An attempt to create a
partitioned tables using a storage engine that does not supply
native partitioning support fails with
ER_CHECK_NOT_IMPLEMENTED.
MySQL 8.0 Community binaries provided by Oracle include
partitioning support provided by the InnoDB and
NDB storage engines. For information about
partitioning support offered in MySQL Enterprise Edition binaries, see
Chapter 30, MySQL Enterprise Edition.
If you are compiling MySQL 8.0 from source, configuring
the build with InnoDB support is sufficient to
produce binaries with partition support for
InnoDB tables. For more information, see
Section 2.9, “Installing MySQL from Source”.
Nothing further needs to be done to enable partitioning support by
InnoDB (for example, no special entries are
required in the my.cnf file).
It is not possible to disable partitioning support by the
InnoDB storage engine.
See Section 23.1, “Overview of Partitioning in MySQL”, for an introduction to partitioning and partitioning concepts.
Several types of partitioning are supported, as well as subpartitioning; see Section 23.2, “Partitioning Types”, and Section 23.2.6, “Subpartitioning”.
Section 23.3, “Partition Management”, covers methods of adding, removing, and altering partitions in existing partitioned tables.
Section 23.3.4, “Maintenance of Partitions”, discusses table maintenance commands for use with partitioned tables.
The PARTITIONS table in the
INFORMATION_SCHEMA database provides information
about partitions and partitioned tables. See
Section 25.17, “The INFORMATION_SCHEMA PARTITIONS Table”, for more information; for some
examples of queries against this table, see
Section 23.2.7, “How MySQL Partitioning Handles NULL”.
For known issues with partitioning in MySQL 8.0, see Section 23.6, “Restrictions and Limitations on Partitioning”.
You may also find the following resources to be useful when working with partitioned tables.
Additional Resources. Other sources of information about user-defined partitioning in MySQL include the following:
This is the official discussion forum for those interested in or experimenting with MySQL Partitioning technology. It features announcements and updates from MySQL developers and others. It is monitored by members of the Partitioning Development and Documentation Teams.
MySQL Partitioning Architect and Lead Developer Mikael Ronström frequently posts articles here concerning his work with MySQL Partitioning and NDB Cluster.
A MySQL news site featuring MySQL-related blogs, which should be of interest to anyone using my MySQL. We encourage you to check here for links to blogs kept by those working with MySQL Partitioning, or to have your own blog added to those covered.
Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/mysql-rf-partitioning.html
The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.
References
These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.
