mariadb/mysql-test/suite/encryption
Marko Mäkelä cad56fbaba MDEV-18733 MariaDB slow start after crash recovery
If InnoDB crash recovery was needed, the InnoDB function srv_start()
would invoke extra validation, reading something from every InnoDB
data file. This should be unnecessary now that MDEV-14717 made
RENAME operations crash-safe inside InnoDB (which can be
disabled in MariaDB 10.2 by setting innodb_safe_truncate=OFF).

dict_check_sys_tables(): Skip tables that would be dropped by
row_mysql_drop_garbage_tables(). Perform extra validation only
if innodb_safe_truncate=OFF, innodb_force_recovery=0 and
crash recovery was needed.

dict_load_table_one(): Validate the root page of the table.
In this way, we can deny access to corrupted or mismatching tables
not only after crash recovery, but also after a clean shutdown.
2019-04-03 19:56:03 +03:00
..
include MDEV-9099: Test encryption.innodb_encryption_discard_import fails on buildbot 2016-10-29 10:09:06 +03:00
r MDEV-18733 MariaDB slow start after crash recovery 2019-04-03 19:56:03 +03:00
t MDEV-18733 MariaDB slow start after crash recovery 2019-04-03 19:56:03 +03:00
disabled.def Disable a frequently failing test 2018-12-04 15:30:04 +02:00
suite.pm move encryption tests to a dedicate suite 2015-05-13 14:27:16 +02:00