Debian Codegraph @

mysql-test/suite/max_parts/r/innodb_partition_open_files_limit.result

raw
1 CALL mtr.add_suppression("innodb_open_files should not be greater than the open_files_limit.");
2 CALL mtr.add_suppression("You must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all");
3 CALL mtr.add_suppression("redo log files and all system tablespace files open for the whole time mysqld is running, and");
4 CALL mtr.add_suppression("needs to open also some .ibd files if the file-per-table storage model is used. Current open files .*, max allowed open files 1.");
5 CALL mtr.add_suppression("Too many (.*) files stay open while the maximum allowed value would be 1. You may need to raise the value of innodb_open_files in my.cnf.");
6 CALL mtr.add_suppression("Cannot close file ./mysql/tables.ibd, because modification");
7 CALL mtr.add_suppression("Open files .* exceeds the limit 1");
8 CALL mtr.add_suppression("Cannot close file");
9 DROP TABLE IF EXISTS `t1`;
10 # Bug#46922: crash when adding partitions and open_files_limit is reached
11 CREATE TABLE t1 (a INT PRIMARY KEY)
12 PARTITION BY KEY () PARTITIONS 1;
13 INSERT INTO t1 VALUES (1), (2), (3), (4), (5), (6), (7), (8), (9), (10), (11);
14 ALTER TABLE t1 ADD PARTITION PARTITIONS 50;
15 SELECT * FROM t1;
16 a
17 1
18 10
19 11
20 2
21 3
22 4
23 5
24 6
25 7
26 8
27 9
28 DROP TABLE t1;