diff options
| author | Marko Mäkelä <marko.makela@mariadb.com> | 2017-01-30 17:00:51 +0200 |
|---|---|---|
| committer | Marko Mäkelä <marko.makela@mariadb.com> | 2017-02-05 17:07:16 +0200 |
| commit | f1627045701b0dc0ff10ec09cca18dc5da351768 (patch) | |
| tree | 6a3aba723cf060c17402dbfb434950d8f0dc6413 /client | |
| parent | 20e8347447d55c06e426821de207091059ebd214 (diff) | |
| download | mariadb-git-f1627045701b0dc0ff10ec09cca18dc5da351768.tar.gz | |
Rewrite the innodb.log_file_size test with DBUG_EXECUTE_IF.
Remove the debug parameter innodb_force_recovery_crash that was
introduced into MySQL 5.6 by me in WL#6494 which allowed InnoDB
to resize the redo log on startup.
Let innodb.log_file_size actually start up the server, but ensure
that the InnoDB storage engine refuses to start up in each of the
scenarios.
Diffstat (limited to 'client')
0 files changed, 0 insertions, 0 deletions