mirror of
https://github.com/MariaDB/server.git
synced 2025-01-16 12:02:42 +01:00
7f04686a2a
As part of MDEV-23855, we eliminated fil_system.LRU and changed the way how InnoDB data files are opened. We are also enforcing the innodb_open_files limit when new data files are created. The function fil_space_t::flush() would be invoked by row_quiesce_table_start(). If the table was already in clean state, it is possible that the data file is not open. fil_space_t::flush_low(): If the data file is not open, check with a debug assertion that there are no unflushed changes, and carry on. Reviewed by: Eugene Kosov and Thirunarayanan Balathandayuthapani
16 lines
512 B
Text
16 lines
512 B
Text
SELECT @@GLOBAL.innodb_open_files;
|
|
@@GLOBAL.innodb_open_files
|
|
10
|
|
CREATE TABLE t0 (a INT) ENGINE=InnoDB;
|
|
FLUSH TABLE t0 WITH READ LOCK;
|
|
UNLOCK TABLES;
|
|
CREATE TABLE t1 (a INT) ENGINE=InnoDB;
|
|
CREATE TABLE t2 (a INT) ENGINE=InnoDB;
|
|
CREATE TABLE t3 (a INT) ENGINE=InnoDB;
|
|
CREATE TABLE t4 (a INT) ENGINE=InnoDB;
|
|
CREATE TABLE t5 (a INT) ENGINE=InnoDB;
|
|
CREATE TABLE t6 (a INT) ENGINE=InnoDB;
|
|
CREATE TABLE t7 (a INT) ENGINE=InnoDB;
|
|
FLUSH TABLE t0 WITH READ LOCK;
|
|
UNLOCK TABLES;
|
|
DROP TABLE t0, t1, t2, t3, t4, t5, t6, t7;
|