[MDEV-17884] Temporary MyISAM table is marked as crashed after re-opening Created: 2018-11-30  Updated: 2019-07-05  Resolved: 2019-07-05

Status: Closed
Project: MariaDB Server
Component/s: Data Definition - Temporary, Storage Engine - MyISAM
Affects Version/s: 10.2, 10.3, 10.4
Fix Version/s: 10.2.26, 10.3.17, 10.4.7

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Michael Widenius
Resolution: Fixed Votes: 0
Labels: affects-tests

Issue Links:
Relates
relates to MDEV-19595 ER_CRASHED_ON_USAGE and Assertion `!i... Closed

 Description    

CREATE TEMPORARY TABLE t1 (f VARCHAR(8)) ENGINE=MyISAM;
 
INSERT INTO t1 () VALUES (),(),(),();
 
INSERT INTO t1 SELECT * FROM t1;
 
DELETE FROM t1 LIMIT 1;
 
OPTIMIZE TABLE t1;
 
INSERT INTO t1 SELECT * FROM t1;
 
INSERT INTO t1 SELECT * FROM t1;

10.2 861038f2e8e

 
OPTIMIZE TABLE t1;
 
Table	Op	Msg_type	Msg_text
 
test.t1	optimize	status	OK
 
INSERT INTO t1 SELECT * FROM t1;
 
INSERT INTO t1 SELECT * FROM t1;
 
bug.crashed3                             [ fail ]
 
        Test ended at 2018-12-01 00:35:53
 
 
 
CURRENT_TEST: bug.crashed3
 
mysqltest: At line 7: query 'INSERT INTO t1 SELECT * FROM t1' failed: 1194: Table 't1' is marked as crashed and should be repaired



 Comments   
Comment by Elena Stepanova [ 2019-05-25 ]

Note: the test case and effect are very similar to MDEV-19595. It's possible that the problem is unrelated to the engine, and one fix will fix them both.

Comment by Elena Stepanova [ 2019-07-05 ]

Fixed along with MDEV-19595.

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