mirror of
https://github.com/MariaDB/server.git
synced 2025-09-05 08:04:25 +03:00
893472d005
The option innodb_rollback_segments was deprecated already in MariaDB Server 10.0. Its misleadingly named replacement innodb_undo_logs is of very limited use. It makes sense to always create and use the maximum number of rollback segments. Let us remove the deprecated parameter innodb_rollback_segments and deprecate&ignore the parameter innodb_undo_logs (to be removed in a later major release). This work involves some cleanup of InnoDB startup. Similar to other write operations, DROP TABLE will no longer be allowed if innodb_force_recovery is set to a value larger than 3.
43 lines
1.0 KiB
Plaintext
43 lines
1.0 KiB
Plaintext
#
|
|
# 2011-08-01 Added
|
|
#
|
|
|
|
--source include/have_innodb.inc
|
|
|
|
#
|
|
# exists as global only
|
|
#
|
|
SELECT @@global.innodb_undo_logs;
|
|
|
|
--error ER_INCORRECT_GLOBAL_LOCAL_VAR
|
|
SELECT @@session.innodb_undo_logs;
|
|
SHOW global variables LIKE 'innodb_undo_logs';
|
|
SHOW session variables LIKE 'innodb_undo_logs';
|
|
--disable_warnings
|
|
SELECT * FROM information_schema.global_variables
|
|
WHERE variable_name='innodb_undo_logs';
|
|
SELECT * FROM information_schema.session_variables
|
|
WHERE variable_name='innodb_undo_logs';
|
|
--enable_warnings
|
|
|
|
SET global innodb_undo_logs=100;
|
|
SELECT @@global.innodb_undo_logs;
|
|
--error ER_GLOBAL_VARIABLE
|
|
SET session innodb_undo_logs=1;
|
|
|
|
#
|
|
# incorrect types
|
|
#
|
|
--error ER_WRONG_TYPE_FOR_VAR
|
|
SET global innodb_undo_logs=1.1;
|
|
--error ER_WRONG_TYPE_FOR_VAR
|
|
SET global innodb_undo_logs=1e1;
|
|
--error ER_WRONG_TYPE_FOR_VAR
|
|
SET global innodb_undo_logs="foo";
|
|
SET global innodb_undo_logs=-7;
|
|
SELECT @@global.innodb_undo_logs;
|
|
--disable_warnings
|
|
SELECT * FROM information_schema.global_variables
|
|
WHERE variable_name='innodb_undo_logs';
|
|
--enable_warnings
|