Partitioning Limitations

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 Using CONNECT - Partitioning and Sharding.

• A partitioned table cannot contain, or be referenced by, foreign keys.

• The query cache 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 binlog_format=ROW 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 MariaDB 11.3.2, it is not possible to create partitions on tables that contain GEOMETRY types.

See Also

• INFORMATION_SCHEMA.PARTITIONS contains information about existing partitions.

• Partition Maintenance for suggestions on using partitions

_{This page is licensed: CC BY-SA / Gnu FDL}