Details
-
New Feature
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
-
Q2/2026 Server Development
Description
Some users would like MariaDB to support interval partitioning similar to Oracle's feature:
Interval Partitioning
Interval partitioning is an extension of range partitioning which instructs the database to automatically create partitions of a specified interval when data inserted into the table exceeds all of the existing range partitions. You must specify at least one range partition. The range partitioning key value determines the high value of the range partitions, which is called the transition point, and the database creates interval partitions for data with values that are beyond that transition point. The lower boundary of every interval partition is the non-inclusive upper boundary of the previous range or interval partition.
For example, if you create an interval partitioned table with monthly intervals and you set the transition point at January 1, 2007, then the lower boundary for the January 2007 interval is January 1, 2007. The lower boundary for the July 2007 interval is July 1, 2007, regardless of whether the June 2007 partition was created.
You can create single-level interval partitioned tables and the following composite partitioned tables:
- Interval-range
- Interval-hash
- Interval-list
- Only one partitioning key column can be specified, and it must be of NUMBER or DATE type.
- Interval partitioning is not supported for index-organized tables.
- NULL values cannot be stored in the partitioning key column when using interval partitioning.
Interval partitioning supports a subset of the capabilities of range partitioning. For information about restrictions when using interval partitioning, refer to Oracle Database SQL Language Reference.
https://docs.oracle.com/database/121/VLDBG/GUID-C121EA1B-2725-4464-B2C9-EEDE0C3C95AB.htm
Attachments
Issue Links
- causes
-
MDEV-39807 MDEV-15621: Assertion `0' failed upon INSERT
-
- Closed
-
-
MDEV-39808 MDEV-15621: ROW-binlog + INSERT: auto-creates an interval partition & logs the row, but not the implicit ADD PARTITION
-
- Closed
-
-
MDEV-40048 MDEV-15621: Prelocking with range interval auto partitioning
-
- Closed
-
-
MDEV-40088 MDEV-15621: Assertion `fixed()' failed with INTERVAL (SELECT 1) DAY
-
- Closed
-
-
MDEV-40467 Auto-partition fails when using maximum timestamp
-
- Closed
-
-
MDEV-40631 main.partition_range_interval timeout in view protocol
-
- Closed
-
-
MDEV-40650 main.partition_range_interval fails 32bit builders
-
- Closed
-
-
MDEV-40978 PREPARE with INTERVAL ? in Partition DDL Crashes the Server (DoS)
-
- Closed
-
-
MDEV-41579 INSERT DELAYED into a table with INTERVAL partitioning hangs
-
- Open
-
-
MDEV-41582 Assertion `!m_prebuilt->table || table->versioned() == m_prebuilt->table->versioned()' failed in ha_innobase::open on INSERT w/ INTERVAL partitioning
-
- Open
-
-
MDEV-41596 Galera node leaves the cluster after an INSERT that adds INTERVAL partitions on another node
-
- Open
-
-
MDEV-41600 INSERT fails with ERROR 1493 when INTERVAL partitions on a TIMESTAMP column cross a change to daylight saving time
-
- Open
-
-
MDEV-41628 INSERT fails with ERROR 1517 when a new INTERVAL partition gets the name of an existing partition or subpartition
-
- Open
-
-
MDEV-41629 INTERVAL partitioning on a TIMESTAMP column changes the query result: a session with another time zone does not find the row
-
- Open
-
-
MDEV-41710 Replica stops with error 1526 on a row event for an INTERVAL partitioned table when the master session has another time zone
-
- In Progress
-
-
MDEV-41711 Concurrent INSERTs each add the missing INTERVAL partitions, so the table gets several times the partitions it needs
-
- Open
-
-
MDEV-41712 Aria or MyISAM table can no longer be opened after SYSTEM_TIME AUTO or INTERVAL partitioning adds partitions without its ROW_FORMAT
-
- Open
-
-
MDEV-41733 A consistent snapshot transaction, and so mariadb-dump --single-transaction, fails with ERROR 1412 after DML in another session adds SYSTEM_TIME AUTO or INTERVAL partitions
-
- Open
-
-
MDEV-41853 INTERVAL 1 MONTH partition bounds drift to the 28th when the first bound is at the end of a month
-
- Open
-
-
MDEV-41858 Warning for a failed INTERVAL partition creation shows %s.%s instead of the table name
-
- Open
-
- is duplicated by
-
MDEV-32057 Auto adding of partitions
-
- Closed
-
- relates to
-
MDEV-17554 Auto-create history partitions for system-versioned tables
-
- Closed
-
- split to
-
MDEV-39666 Test MDEV-15621 Implement interval partitioning similar to Oracle
-
- In Testing
-
- has action item
-
DOCS-6233 Loading...