mirror of
https://github.com/MariaDB/server.git
synced 2025-02-12 00:15:35 +01:00
e581396b7a
Before commit6112853cdain 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 commitb5852ffbee. Starting with commitbaf276e6d4(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 commit86dc7b4d4c(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.
46 lines
2 KiB
Text
46 lines
2 KiB
Text
--source include/have_innodb.inc
|
|
#
|
|
# Bug#39438 Testcase for Bug#39436 crashes on 5.1 in fil_space_get_latch
|
|
# http://bugs.mysql.com/39438
|
|
#
|
|
|
|
SET default_storage_engine=InnoDB;
|
|
|
|
# we care only that the following SQL commands do not crash the server
|
|
-- disable_query_log
|
|
-- disable_result_log
|
|
|
|
DROP TABLE IF EXISTS bug39438;
|
|
|
|
CREATE TABLE bug39438 (id INT) ENGINE=INNODB;
|
|
|
|
# remove: XXX Uncomment the following ALTER and remove those lines after
|
|
# remove: applying the patch.
|
|
# remove: Obviously this test is useless without this ALTER command,
|
|
# remove: but it causes warnings to be printed by mysqld and the whole
|
|
# remove: mysql-test suite fails at the end (returns non-zero). Please
|
|
# remove: apply this patch to the mysql source tree, remove those lines
|
|
# remove: and uncomment the following ALTER. We do not care about the
|
|
# remove: warnings, this test is to ensure mysqld does not crash.
|
|
# remove: === modified file 'mysql-test/lib/mtr_report.pl'
|
|
# remove: --- mysql-test/lib/mtr_report.pl 2008-08-12 10:26:23 +0000
|
|
# remove: +++ mysql-test/lib/mtr_report.pl 2008-10-01 11:57:41 +0000
|
|
# remove: @@ -412,7 +412,10 @@
|
|
# remove:
|
|
# remove: # When trying to set lower_case_table_names = 2
|
|
# remove: # on a case sensitive file system. Bug#37402.
|
|
# remove: - /lower_case_table_names was set to 2, even though your the file system '.*' is case sensitive. Now setting lower_case_table_names to 0 to avoid future problems./
|
|
# remove: + /lower_case_table_names was set to 2, even though your the file system '.*' is case sensitive. Now setting lower_case_table_names to 0 to avoid future problems./ or
|
|
# remove: +
|
|
# remove: + # this test is expected to print warnings
|
|
# remove: + ($testname eq 'main.innodb_bug39438')
|
|
# remove: )
|
|
# remove: {
|
|
# remove: next; # Skip these lines
|
|
# remove:
|
|
#ALTER TABLE bug39438 DISCARD TABLESPACE;
|
|
|
|
# this crashes the server if the bug is present
|
|
SHOW TABLE STATUS;
|
|
|
|
DROP TABLE bug39438;
|