diff options
author | Marko Mäkelä <marko.makela@mariadb.com> | 2019-10-11 08:24:30 +0300 |
---|---|---|
committer | Marko Mäkelä <marko.makela@mariadb.com> | 2019-10-11 08:24:30 +0300 |
commit | b05be3ef8c8668ddbcbe8e1c08dcd4fcc88eb4cf (patch) | |
tree | 0aae463b0d11beb342c859b144fbb21b7a649e49 /scripts/mysqld_multi.sh | |
parent | 09afd3da1a80e403b5375845770dde61832afa50 (diff) | |
download | mariadb-git-b05be3ef8c8668ddbcbe8e1c08dcd4fcc88eb4cf.tar.gz |
Add encryption.innodb-redo-badkey,strict_full_crc32
In commit 0f7732d1d1d898f1a9051858932c18bcc9d6f2b4
we introduced a innodb_checksum_algorithm=full_crc32 combination
to a number of encryption tests, and also fixed the code accordingly.
The default in MariaDB 10.5 is innodb_checksum_algorithm=full_crc32.
In a test merge to 10.5, the test encryption.innodb-redo-badkey failed
once due to a message that had been added in that commit.
Let us introduce a full_crc32 option to that test.
And let us use strict_crc32 and strict_full_crc32 instead of the
non-strict variants, for the previously augmented tests, to be in
line with the earlier tests encryption.corrupted_during_recovery and
encryption.innodb_encrypt_temporary_tables.
Diffstat (limited to 'scripts/mysqld_multi.sh')
0 files changed, 0 insertions, 0 deletions