mariadb/innodb_scrub_background.opt at 0806592ac8fb7c6071defccb51e762a89f5bd8d9 - mariadb - GitFox

database/mariadb

mirror of https://github.com/MariaDB/server.git synced 2025-05-01 08:45:04 +03:00

Marko Mäkelä 069d0472b3 MDEV-12762 Some files in current 10.2 tree seem to be reverted to an old state

The issue was a bad merge of MDEV-12253 from 10.1 to 10.2
in commit f9cc391863ab962e8c8a8a8a676d730498eb8d6f.
In that merge, I wrongly assumed that all test file conflicts
for mysql-test/suite/encryption had been properly resolved in
bb-10.2-MDEV-12253 (commit 76aa6be77635c7017459ce33b41c837c9acb606d)
while in fact, some files there had been copied from the 10.1 branch.

This commit is based on a manually done conflict resolution of
the mysql-test/suite/encryption on the same merge, applied to
the current 10.2 branch.

As part of this commit, the test encryption.innodb-bad-key-change4
which was shortly disabled due to MDEV-11336 will be re-enabled again.
(While the test enables innodb_defragment, it does not fail even though
enabling innodb_defragment currently has no effect.)

2017-05-10 09:06:57 +03:00

8 lines

268 B

Plaintext

Raw Blame History

 --innodb-immediate-scrub-data-uncompressed=OFF
 --innodb-background-scrub-data-uncompressed=ON
 --innodb-background-scrub-data-compressed=ON
 --loose-innodb-debug-force-scrubbing=ON
 --innodb-encryption-threads=0
 --innodb-encrypt-tables=OFF
 --innodb-tablespaces-scrubbing