mariadb/mysql-test/suite/innodb/t/innodb_bug12400341-master.opt at 415797f1a67d5281c4e585ac3dc82b10e5dcbd16 - mirror/mariadb - May the force be without you: git.fucktheforce.de

mirror/mariadb

mirror of https://github.com/MariaDB/server.git synced 2025-01-30 18:41:56 +01:00

Marko Mäkelä 893472d005 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.

2019-05-23 17:34:47 +03:00

1 line

51 B

Text

Raw Blame History

--max_connections=64 --innodb_thread_concurrency=0