Debian Codegraph @

mysql-test/suite/innodb/r/log_file_truncate_2.result

raw
1 CREATE TABLE t(a INT PRIMARY KEY, b INT);
2 INSERT INTO t(a, b) VALUES(1, 1);
3 # Resize redo log to 100M:
4 SET GLOBAL innodb_redo_log_capacity = 100*1024*1024;
5 SET GLOBAL innodb_log_checkpoint_now = 1;
6 # Create connection which generates spam to the redo log.
7 CALL log_spammer();
8 CALL log_spammer();
9 # Wait until redo occupies at least 10MB on disk
10 SET GLOBAL DEBUG = 'd,log_force_truncate';
11 # Resize redo log to 8M with usage of truncate (in background spammer keeps adding to redo!):
12 SET GLOBAL innodb_redo_log_capacity = 8*1024*1024;
13 # Waiting for status = OK....
14 Pattern "Truncating redo log file" found
15 UPDATE t SET b = 2 WHERE a = 1;
16 CALL mtr.add_suppression("The last block of redo had corrupted first_rec_group");
17 # Kill and restart
18 SELECT * FROM t;
19 a b
20 1 2
21 DROP TABLE t;