database/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-08-08 11:22:35 +03:00
Code Activity

MDEV-21870 Deprecate and ignore innodb_scrub_log and innodb_scrub_log_speed

Browse Source 
The configuration parameter innodb_scrub_log never really worked, as
reported in MDEV-13019 and MDEV-18370.

Because MDEV-14425 is changing the redo log format, the innodb_scrub_log
feature would have to be adjusted for it. Due to the known problems,
it is easier to remove the feature for now, and to ignore and deprecate
the parameters.

If old log contents should be kept secret, then enabling innodb_encrypt_log
or setting a smaller innodb_log_file_size could help.
This commit is contained in:
Marko Mäkelä
2020-03-04 17:06:49 +02:00
parent d62766a890
commit 64be4ab4a8
11 changed files with 43 additions and 175 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
mysql-test/suite/encryption/r/innodb-scrub-log.result
View File

@@ -1,3 +0,0 @@
create table t1(a int not null primary key auto_increment,
b varchar(200), c char(100), d varchar(150)) engine=innodb;
DROP TABLE t1;

1
mysql-test/suite/encryption/t/innodb-scrub-log.opt
View File

@@ -1 +0,0 @@
--loose-innodb-scrub-log=on

13
mysql-test/suite/encryption/t/innodb-scrub-log.test
View File

@@ -1,13 +0,0 @@
--source include/have_innodb.inc
#
# MDEV-11705: InnoDB: Failing assertion: (&log_sys.mutex)->is_owned() if server started with innodb-scrub-log
#
create table t1(a int not null primary key auto_increment,
b varchar(200), c char(100), d varchar(150)) engine=innodb;
let $wait_condition= SELECT variable_value FROM information_schema.global_status WHERE variable_name = 'innodb_scrub_log';
--source include/wait_condition.inc
DROP TABLE t1;