This page outlines constraints when using partitioning, such as the maximum number of partitions and restrictions on foreign keys and query cache usage.
The following limitations apply to partitioning in MariaDB:
Each table can contain a maximum of 8192 partitions.
Queries are never parallelized, even when they involve multiple partitions.
A table can only be partitioned if the storage engine supports partitioning.
All partitions must use the same storage engine. For a workaround, see .
A partitioned table cannot contain, or be referenced by, .
The is not aware of partitioning and partition pruning. Modifying a partition will invalidate the entries related to the whole table.
Updates can run more slowly when and a partitioned table is updated than an equivalent update of a non-partitioned table.
All columns used in the partitioning expression for a partitioned table must be part of every unique key that the table may have.
In versions prior to , it is not possible to create partitions on tables that contain .
contains information about existing partitions.
for suggestions on using partitions
This page is licensed: CC BY-SA / Gnu FDL