mirror of
https://github.com/MariaDB/server.git
synced 2025-11-25 17:25:02 +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.
16 lines
521 B
Plaintext
16 lines
521 B
Plaintext
SET GLOBAL innodb_undo_log_truncate = 1;
|
|
SET GLOBAL innodb_purge_rseg_truncate_frequency = 1;
|
|
create table t1(keyc int primary key, c char(100)) engine = innodb;
|
|
begin;
|
|
commit;
|
|
begin;
|
|
update t1 set c = 'MariaDB';
|
|
update t1 set c = 'InnoDB';
|
|
set global debug_dbug = '+d,ib_undo_trunc';
|
|
commit;
|
|
call mtr.add_suppression("InnoDB: innodb_undo_tablespaces=0 disables dedicated undo log tablespaces");
|
|
SET GLOBAL innodb_fast_shutdown=0;
|
|
FOUND 1 /ib_undo_trunc/ in mysqld.1.err
|
|
# restart: with restart_parameters
|
|
drop table t1;
|