Bug #46617 | Bogus "table is marked as crashed and should be repaired" | ||
---|---|---|---|
Submitted: | 8 Aug 2009 12:46 | Modified: | 11 May 2011 8:36 |
Reporter: | Philip Stoev | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Server: DDL | Severity: | S3 (Non-critical) |
Version: | 5.1 | OS: | Any |
Assigned to: | Jon Olav Hauglid | CPU Architecture: | Any |
[8 Aug 2009 12:46]
Philip Stoev
[10 Aug 2009 20:24]
Philip Stoev
Engine is MyISAM, the default engine for mysql :-) . If some other engine was used, it would have been visible from the test case. Also, this is the only engine that exhibits this message. This test is non-concurrent and the commands are run sequentially. Due to the automatic nature of the test, after simplification some unnecessary queries may have remained.
[14 Aug 2009 16:31]
MySQL Verification Team
triage, kindly retriage this bug. Because original testcase was unreadable, here, for your ease of reading I made a better testcase that shows the problem. --------------- drop database if exists test; create database test; use test; create table t1 (`a` int) engine=myisam select 5; create table t2 (`a` int) engine=myisam select 1; create table t3 (`a` int) engine=myisam select 1; create or replace view v1 as select `a` from t1 union select `a` from `t3`; delimiter | create trigger `trg` after insert on `t3` for each row begin select * from `v1` limit 0 into @a ; end| delimiter ; create table if not exists `t3` as select `a` from t1; --------------- As you see, the trigger on t3 refers to a view which access t3. during the create table, i guess mysql gets confused as to the state of t3 :)
[17 Sep 2009 10:42]
Matthias Leich
Bug#47381 Wrong warning about crashed table, CREATE TABLE IF NOT EXISTS AS SELECT was marked as duplicate of this bug
[1 Nov 2010 15:35]
Jon Olav Hauglid
Not able to repeat this bug with current version of 5.5 (5.5-bugteam). Still able to repeat it with 5.1 (5.1-bugteam). Tested both with the test case posted here and the test case from Bug#47381.
[1 Nov 2010 16:15]
MySQL Verification Team
I concur. Just tested 5.1.53 and it gives table marked as crashed error. but it is not repeatable anymore on current mysql-5.5-security tree
[11 May 2011 8:36]
Jon Olav Hauglid
A 5.1 only bug that's triaged to be fixed only in trunk, means there's nothing to fix. Closing the bug as "Won't fix".