mariadb/mysql-test/suite/innodb/r/innodb_bug14147491.result
Michael Widenius b5615eff0d Write information about restart in .result
Idea comes from MySQL which does something similar
2019-04-01 19:47:24 +03:00

21 lines
741 B
Text

# Ensure that purge will not crash on the table after we corrupt it.
SET GLOBAL innodb_purge_rseg_truncate_frequency = 1;
SET GLOBAL innodb_fast_shutdown=0;
# 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.
# restart
# 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;