From 9608773f75e2ca21491ef6825c3616cdc96d1ca5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marko=20M=C3=A4kel=C3=A4?= Date: Tue, 31 Aug 2021 13:55:02 +0300 Subject: MDEV-4750 follow-up: Reduce disabling innodb_stats_persistent This essentially reverts commit 4e89ec6692786bc1cbdce64d43d8e85a5d247dab and only disables InnoDB persistent statistics for tests where it is desirable. By design, InnoDB persistent statistics will not be updated except by ANALYZE TABLE or by STATS_AUTO_RECALC. The internal transactions that update persistent InnoDB statistics in background tasks (with innodb_stats_auto_recalc=ON) may cause nondeterministic query plans or interfere with some tests that deal with other InnoDB internals, such as the purge of transaction history. --- mysql-test/main/mysql_upgrade.test | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'mysql-test/main/mysql_upgrade.test') diff --git a/mysql-test/main/mysql_upgrade.test b/mysql-test/main/mysql_upgrade.test index ae1b328e699..10dddbe7943 100644 --- a/mysql-test/main/mysql_upgrade.test +++ b/mysql-test/main/mysql_upgrade.test @@ -367,7 +367,7 @@ rename table mysql.global_priv_bak to mysql.global_priv; --echo # # The warning appears during mysql_upgrade, before the schema becomes consistent -call mtr.add_suppression("innodb_table_stats has length mismatch in the column name table_name"); +call mtr.add_suppression("innodb_(table|index)_stats has length mismatch in the column name table_name"); # This comes from opening 10.6 sys.host_summary view that uses sys.format_time function, # on still inconsistent mysql.proc, in older versions call mtr.add_suppression("Column count of mysql.proc is wrong. Expected 21, found 20."); -- cgit v1.2.1