mariadb/mysql-test/suite/encryption/t/innodb_encrypt_log.opt at 97cd583df7f118673bf28a9afaffe5dafcd1b4e9 - mirror/mariadb - May the force be without you: git.fucktheforce.de

mirror/mariadb

mirror of https://github.com/MariaDB/server.git synced 2025-01-16 12:02:42 +01:00

Marko Mäkelä 06b4b99f3e The test failed once on Buildbot with the result difference:

# ib_logfile0 expecting FOUND
-FOUND 3 /public|gossip/ in ib_logfile0
+FOUND 2 /public|gossip/ in ib_logfile0

The most plausible explanation for this difference
should be that the redo log payload grew was so big that
one of the strings (for writing the undo log record,
clustered index record, and secondary index record)
was written to ib_logfile1 instead of ib_logfile0.

Let us run the test with --innodb-log-files-in-group=1 so that
only a single log file will be used.

2017-08-23 14:40:23 +03:00

7 lines

278 B

Text

Raw Blame History

 --innodb-encrypt-log=ON
 --innodb-encrypt-tables=FORCE
 --plugin-load-add=$FILE_KEY_MANAGEMENT_SO
 --loose-file-key-management
 --loose-file-key-management-filename=$MYSQL_TEST_DIR/std_data/logkey.txt
 --innodb-log-files-in-group=1
 --file-key-management-encryption-algorithm=aes_cbc