mariadb/mysql-test/suite/innodb/r/innodb_bug14147491.result
Jan Lindström f0eb8f153d 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.
2017-05-08 14:03:49 +03:00

17 lines
574 B
Text

# Create and populate the table to be corrupted
set global innodb_file_per_table=ON;
CREATE TABLE t1 (a INT AUTO_INCREMENT PRIMARY KEY, b TEXT) ENGINE=InnoDB;
INSERT INTO t1 (b) VALUES ('corrupt me');
INSERT INTO t1 (b) VALUES ('corrupt me');
# Corrupt the table
Munged a string.
Munged a string.
# Now t1 is corrupted but we should not crash
SELECT * FROM t1;
Got one of the listed errors
INSERT INTO t1(b) VALUES('abcdef');
Got one of the listed errors
UPDATE t1 set b = 'deadbeef' where a = 1;
Got one of the listed errors
# Cleanup, this must be possible
DROP TABLE t1;