[MDEV-21507] ER_CRASHED_ON_USAGE upon DML and OPTIMIZE on temporary Aria table Created: 2020-01-17  Updated: 2023-07-28  Resolved: 2023-07-28

Status: Closed
Project: MariaDB Server
Component/s: Data Definition - Temporary, Storage Engine - Aria
Affects Version/s: 5.5, 10.1
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Michael Widenius
Resolution: Won't Fix Votes: 0
Labels: not-10.2, not-10.3, not-10.4

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

 Description   

Note: There was a very similar bug MDEV-19595. However the test case there was only failing on 10.2+, so the bug was fixed in 10.2+. The test case below reveals the same problem on 5.5 and 10.1. On 10.2+ it stopped failing after the fix for MDEV-19595, so it's apparently the same problem. I don't expect it to be fixed in 10.1 which is at the moment 3 major releases behind the latest one; but tests on 10.1 are still running, and the bug affects them, so I need it to be filed. It will quietly expire when 5.5 and 10.1 go EOL.

CREATE TEMPORARY TABLE t1 (a INT) ROW_FORMAT=DYNAMIC ENGINE=Aria;
INSERT INTO t1 VALUES (1);
DELETE FROM t1 LIMIT 2;
OPTIMIZE TABLE t1;
INSERT INTO t1 VALUES (2);
DELETE FROM t1 LIMIT 2;

10.1 cb204e11

mysqltest: At line 6: query 'DELETE FROM t1 LIMIT 2' failed: 1194: Table 't1' is marked as crashed and should be repaired



 Comments   
Comment by Elena Stepanova [ 2023-07-28 ]

10.1 is EOL

Generated at Thu Feb 08 09:07:40 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.