Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.3
-
None
Description
Note: I think it has been discussed before, but I can't find it in JIRA. If you know the original, please feel free to close this one as a duplicate.
When history partitions are over-populated, server starts throwing warnings upon any DML operations, including those which don't add anything to history partitions. At the very least it should be documented, although I expect that users will complain about it even if it's documented, because it's counter-intuitive.
create or replace table t1 (a int) engine=MyISAM with system versioning partition by system_time limit 2 (partition p0 history, partition pc current); |
insert into t1 values (1),(2),(3); |
delete from t1; |
insert into t1 values (4); |
|
10.3 c39f8a80c9 |
MariaDB [db1]> insert into t1 values (4); |
Query OK, 1 row affected, 1 warning (0.01 sec)
|
 |
MariaDB [db1]> show warnings;
|
+---------+------+---------------------------------------------------------------------------------+ |
| Level | Code | Message | |
+---------+------+---------------------------------------------------------------------------------+ |
| Warning | 4114 | Versioned table `db1`.`t1`: partition `p0` is full, add more HISTORY partitions | |
+---------+------+---------------------------------------------------------------------------------+ |
1 row in set (0.00 sec) |