[MDEV-15992] WARN_VERS_PART_FULL is issued even upon INSERT, when history partitions are not used Created: 2018-04-23  Updated: 2023-04-27

Status: Open
Project: MariaDB Server
Component/s: Documentation, Partitioning, Versioned Tables
Affects Version/s: 10.3
Fix Version/s: 10.4

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Sergei Golubchik
Resolution: Unresolved Votes: 0
Labels: 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)


Generated at Thu Feb 08 08:25:33 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.