diff options
| author | Marko Mäkelä <marko.makela@mariadb.com> | 2019-05-23 17:34:08 +0300 |
|---|---|---|
| committer | Marko Mäkelä <marko.makela@mariadb.com> | 2019-05-23 17:34:47 +0300 |
| commit | 893472d005b6c62209b15b0955af01a55069d8ef (patch) | |
| tree | 72f257ae8d3d5c380711ac745feaff5e31c74d62 /mysql-test/suite/innodb/t/undo_truncate_recover.test | |
| parent | c83018751cc8eed11279eb6df555bd66c153fa9a (diff) | |
| download | mariadb-git-893472d005b6c62209b15b0955af01a55069d8ef.tar.gz | |
MDEV-19570 Deprecate and ignore innodb_undo_logs, remove innodb_rollback_segments
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.
Diffstat (limited to 'mysql-test/suite/innodb/t/undo_truncate_recover.test')
| -rw-r--r-- | mysql-test/suite/innodb/t/undo_truncate_recover.test | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/mysql-test/suite/innodb/t/undo_truncate_recover.test b/mysql-test/suite/innodb/t/undo_truncate_recover.test index a143c25eaf0..2bcf031f02f 100644 --- a/mysql-test/suite/innodb/t/undo_truncate_recover.test +++ b/mysql-test/suite/innodb/t/undo_truncate_recover.test @@ -11,7 +11,6 @@ # Tests with embedded server do not support restarting --source include/not_embedded.inc -SET GLOBAL innodb_undo_logs = 4; SET GLOBAL innodb_undo_log_truncate = 1; SET GLOBAL innodb_purge_rseg_truncate_frequency = 1; |