diff options
| author | Aleksey Midenkov <midenok@gmail.com> | 2019-12-02 11:48:37 +0300 |
|---|---|---|
| committer | Aleksey Midenkov <midenok@gmail.com> | 2019-12-02 11:48:37 +0300 |
| commit | a7cf0db3d866d92ca54d4ba5f15f3cc3f8b48d31 (patch) | |
| tree | 91cb6d2ce0aea0d081a4ec747d3034330a3767bb /mysql-test/suite/versioning/t/partition.test | |
| parent | 6dd41e008eb2e384913d970e79aa01cd886891ec (diff) | |
| download | mariadb-git-a7cf0db3d866d92ca54d4ba5f15f3cc3f8b48d31.tar.gz | |
MDEV-21011 Table corruption reported for versioned partitioned table after DELETE: "Found a misplaced row"
LIMIT history partitions cannot be checked by existing algorithm of
check_misplaced_rows() because working history partition is
incremented each time another one is filled. The existing algorithm
gets record and tries to decide partition id for it by
get_partition_id(). For LIMIT history it will just get first
non-filled partition.
To fix such partitions it is required to do REBUILD instead of REPAIR.
Diffstat (limited to 'mysql-test/suite/versioning/t/partition.test')
| -rw-r--r-- | mysql-test/suite/versioning/t/partition.test | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/mysql-test/suite/versioning/t/partition.test b/mysql-test/suite/versioning/t/partition.test index ce8c2e5ec1a..5b23d893974 100644 --- a/mysql-test/suite/versioning/t/partition.test +++ b/mysql-test/suite/versioning/t/partition.test @@ -531,4 +531,19 @@ update t1 set a= 'bar' limit 4; select * from t1; drop table t1; +--echo # +--echo # MDEV-21011 Table corruption reported for versioned partitioned table after DELETE: "Found a misplaced row" +--echo # +create table t1 (a int) with system versioning +partition by system_time limit 3 +(partition p1 history, partition p2 history, partition pn current); +insert into t1 values (1),(2),(3),(4); +delete from t1; +delete from t1; +check table t1; + +# cleanup +drop table t1; + + --source suite/versioning/common_finish.inc |