[MDEV-16023] Unfortunate error message WARN_VERS_PART_FULL (partition <name> is full) when rotation time for the last interval passed Created: 2018-04-25  Updated: 2020-08-11  Resolved: 2020-07-29

Status: Closed
Project: MariaDB Server
Component/s: Partitioning, Versioned Tables
Affects Version/s: 10.3
Fix Version/s: 10.3.24, 10.4.14, 10.5.5

Type: Bug Priority: Trivial
Reporter: Elena Stepanova Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: None


 Description    

create or replace table t1 (a int) with system versioning 
partition by system_time interval 1 second (
 
  partition p0 history, 
  partition p1 history, 
  partition pc current
 
);
 
-- wait for 3 seconds
 
insert into t1 values (1),(2),(3);
 
show warnings;

10.3 9f84451d87

 
+---------+------+----------------------------------------------------------------------------------+
 
| Level   | Code | Message                                                                          |
 
+---------+------+----------------------------------------------------------------------------------+
 
| Warning | 4114 | Versioned table `test`.`t1`: partition `p1` is full, add more HISTORY partitions |
 
+---------+------+----------------------------------------------------------------------------------+
 
1 row in set (0.00 sec)

The warning is not wrong (apart being thrown at a strange time, when no historical rows are created; but for that we have a separate JIRA item). However, the text is confusing – the partition is not full, it's just expired.

 Comments   
Comment by Nikita Malyavin [ 2018-07-30 ]

I think no warning should be here. All the data is just added into pn, and p1, p2 are not even touched

Comment by Daniel Black [ 2020-07-29 ]

nikitamalyavin there's a PR https://github.com/MariaDB/server/pull/825 waiting that seems to agree with your previous comment. Do you think its correct? Can you merge it?

Comment by Nikita Malyavin [ 2020-07-29 ]

danblack Thanks! Merged. And added the test you asked

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