1
0
mirror of https://github.com/MariaDB/server.git synced 2025-08-07 00:04:31 +03:00

MDEV-12628: innodb.innodb_bug14147491 sporadically fails in buildbot due to wrong error number

Actual error number returned from the query depends what point
corrupted page is accessed, is it accessed when we read
one of the pages for result set or is it accessed during
background page read.
This commit is contained in:
Jan Lindström
2017-05-08 12:04:08 +03:00
parent 1e227d8880
commit f0eb8f153d
2 changed files with 13 additions and 18 deletions

View File

@@ -6,17 +6,12 @@ INSERT INTO t1 (b) VALUES ('corrupt me');
# Corrupt the table
Munged a string.
Munged a string.
# The below SELECT query will return that table is not
# in engine because table is corrupted
# Now t1 is corrupted but we should not crash
SELECT * FROM t1;
ERROR 42S02: Table 'test.t1' doesn't exist in engine
Got one of the listed errors
INSERT INTO t1(b) VALUES('abcdef');
ERROR 42S02: Table 'test.t1' doesn't exist in engine
Got one of the listed errors
UPDATE t1 set b = 'deadbeef' where a = 1;
ERROR 42S02: Table 'test.t1' doesn't exist in engine
CHECK TABLE t1;
Table Op Msg_type Msg_text
test.t1 check Error Table 'test.t1' doesn't exist in engine
test.t1 check status Operation failed
# Cleanup
Got one of the listed errors
# Cleanup, this must be possible
DROP TABLE t1;