[MDEV-15380] Index for versioned table gets corrupt after partitioning and DELETE Created: 2018-02-21  Updated: 2018-12-17  Resolved: 2018-05-23

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

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

Issue Links:
Blocks
is blocked by MDEV-15923 option to control who can set session... Closed
Relates
relates to MDEV-15458 Segfault in heap_scan() upon UPDATE a... Closed
relates to MDEV-16231 make DELETE use mysql_update() intern... Closed

 Description   

Note: The test is non-deterministic, run with --repeat. It fails for me within 10 attempts, but it can vary on different machines. ASAN or Valgrind don't help.

--source include/have_partition.inc
 
CREATE TABLE t1 (pk INT PRIMARY KEY) ENGINE=MyISAM WITH SYSTEM VERSIONING;
INSERT INTO t1 VALUES (11),(12);
ALTER TABLE t1 PARTITION BY KEY() PARTITIONS 3;
DELETE FROM t1 WHERE pk >= 0;
 
# Cleanup
DROP TABLE t1;

10.3 9d97e6010eb

mysqltest: At line 6: query 'DELETE FROM t1 WHERE pk >= 0' failed: 126: Index for table './test/t1#P#p1.MYI' is corrupt; try to repair it

Also reproducible with Aria. Could not reproduce with InnoDB.



 Comments   
Comment by Eugene Kosov (Inactive) [ 2018-04-16 ]

https://github.com/MariaDB/server/pull/705

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