Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.0, 10.1
-
10.1.20
Description
CREATE OR REPLACE TABLE t |
(
|
id INT UNSIGNED NOT NULL AUTO_INCREMENT, |
timestamp DATETIME NOT NULL, |
PRIMARY KEY (id, timestamp) |
)
|
ENGINE = InnoDB
|
PARTITION BY RANGE (YEAR(timestamp)) |
(
|
PARTITION p0 VALUES LESS THAN (2010), |
PARTITION p1 VALUES LESS THAN (2015), |
PARTITION p2 VALUES LESS THAN (2020) |
);
|
 |
MariaDB [test]> EXPLAIN PARTITIONS INSERT INTO t (id, timestamp) VALUES (NULL, NOW()); |
+------+-------------+-------+------------+------+---------------+------+---------+------+------+-------+ |
| id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | Extra | |
+------+-------------+-------+------------+------+---------------+------+---------+------+------+-------+ |
| 1 | INSERT | t | NULL | ALL | NULL | NULL | NULL | NULL | NULL | NULL | |
+------+-------------+-------+------------+------+---------------+------+---------+------+------+-------+ |
1 row in set (0.00 sec) |
Only tested on 10.0.
Attachments
Issue Links
- relates to
-
MDEV-8982 Apparently UPDATE and DELETE don't use partition pruning
-
- Closed
-