Marko Mäkelä e581396b7a MDEV-29983 Deprecate innodb_file_per_table ... Before commit 6112853cda in MySQL 4.1.1 introduced the parameter innodb_file_per_table, all InnoDB data was written to the InnoDB system tablespace (often named ibdata1). A serious design problem is that once the system tablespace has grown to some size, it cannot shrink even if the data inside it has been deleted. There are also other design problems, such as the server hang MDEV-29930 that should only be possible when using innodb_file_per_table=0 and innodb_undo_tablespaces=0 (storing both tables and undo logs in the InnoDB system tablespace). The parameter innodb_change_buffering was deprecated in commit b5852ffbee. Starting with commit baf276e6d4 (MDEV-19229) the number of innodb_undo_tablespaces can be increased, so that the undo logs can be moved out of the system tablespace of an existing installation. If all these things (tables, undo logs, and the change buffer) are removed from the InnoDB system tablespace, the only variable-size data structure inside it is the InnoDB data dictionary. DDL operations on .ibd files was optimized in commit 86dc7b4d4c (MDEV-24626). That should have removed any thinkable performance advantage of using innodb_file_per_table=0. Since there should be no benefit of setting innodb_file_per_table=0, the parameter should be deprecated. Starting with MySQL 5.6 and MariaDB Server 10.0, the default value is innodb_file_per_table=1.		2023-01-11 17:55:56 +02:00
..
inc	Merge 10.10 into 10.11	2022-12-14 09:18:30 +02:00
r	MDEV-29983 Deprecate innodb_file_per_table	2023-01-11 17:55:56 +02:00
t	MDEV-29983 Deprecate innodb_file_per_table	2023-01-11 17:55:56 +02:00
disabled.def