Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Cannot Reproduce
-
10.3(EOL), 10.4(EOL)
-
None
Description
Note: MDEV-21011 has already been fixed in all branches.
--source include/have_innodb.inc
|
--source include/have_partition.inc
|
 |
CREATE TABLE t1 (pk INT PRIMARY KEY) WITH SYSTEM VERSIONING ENGINE=InnoDB PARTITION BY KEY() PARTITIONS 3; |
INSERT INTO t1 VALUES (1),(2); |
ALTER TABLE t1 DROP SYSTEM VERSIONING; |
CHECK TABLE t1; |
|
# Cleanup
|
DROP TABLE t1; |
10.3 b0fa3080 |
CHECK TABLE t1;
|
Table Op Msg_type Msg_text
|
test.t1 check error Found a misplaced row
|
test.t1 check error Partition p1 returned error
|
test.t1 check error Upgrade required. Please do "REPAIR TABLE `t1`" or dump/reload to fix it!
|
Reproducible on 10.3-10.5 with at least MyISAM and InnoDB.
Attachments
Issue Links
- relates to
-
MDEV-17091 Assertion `old_part_id == m_last_part' failed in ha_partition::update_row or `part_id == m_last_part' in ha_partition::delete_row upon UPDATE/DELETE after dropping versioning
- Closed
-
MDEV-22413 Server hangs upon UPDATE/DELETE on a view reading from versioned partitioned table
- Closed
-
MDEV-21011 CHECK command wrongly reports table corruption
- Closed