Marko Mäkelä 44dce3b207 MDEV-29986 Set innodb_undo_tablespaces=3 by default ... Starting with commit baf276e6d4 (MDEV-19229) the parameter innodb_undo_tablespaces can be increased from its previous default value 0 while allowing an upgrade from old databases. We will change the default setting to innodb_undo_tablespaces=3 so that the space occupied by possible bursts of undo log records can be reclaimed after SET GLOBAL innodb_undo_log_truncate=ON. We will not enable innodb_undo_log_truncate by default, because it causes some observable performance degradation. Special thanks to Thirunarayanan Balathandayuthapani for diagnosing and fixing a number of bugs related to this new default setting. Tested by: Matthias Leich, Axel Schwenke, Vladislav Vaintroub (with both values of innodb_undo_log_truncate)		2023-01-13 12:46:30 +02:00
..
mysql-test/vault	MDEV-29986 Set innodb_undo_tablespaces=3 by default	2023-01-13 12:46:30 +02:00
CMakeLists.txt	MDEV-28819 Statically compiled encryption plugins do not work	2022-06-20 16:37:49 +02:00
hashicorp_key_management.cnf	MDEV-28276: Hashicorp: checking that kv storage is created with version 2+	2022-05-09 07:55:41 +02:00
hashicorp_key_management.txt	MDEV-28276: Hashicorp: checking that kv storage is created with version 2+	2022-05-09 07:55:41 +02:00
hashicorp_key_management_plugin.cc	Further tweaking the alloca handling in Hashicorp plugin	2022-10-26 17:21:23 +11:00