An error occurred fetching the project authors.
- 27 Jan, 2017 1 commit
-
-
Marko Mäkelä authored
As noted in MDEV-8841, any test that kills the server must issue FLUSH TABLES, so that tables of crash-unsafe storage engines will not be corrupted. Consistently issue this statement after any call mtr.add_suppression() calls. Also, do not invoke shutdown_server directly, but use helpers instead.
-
- 15 Jan, 2017 1 commit
-
-
Marko Mäkelä authored
contains a bad and a good copy Clean up the InnoDB doublewrite buffer code. buf_dblwr_init_or_load_pages(): Do not add empty pages to the buffer. buf_dblwr_process(): Do consider changes to pages that are all zero. Do not abort when finding a corrupted copy of a page in the doublewrite buffer, because there could be multiple copies in the doublewrite buffer, and only one of them needs to be good.
-
- 30 Sep, 2016 1 commit
-
-
Jan Lindström authored
Test crashes server intentionally, need to be prepared for crash recovery and database page corruption.
-
- 24 Sep, 2015 1 commit
-
-
Elena Stepanova authored
The real problem is that when innodb.xa_recovery test intentionally crashes the server, system tables can be opened and marked as crashed, and the next test in line gets blamed for the error which appears in the error log. Fixed by flushing the tables before crashing the server
-
- 09 Apr, 2015 2 commits
-
-
Marko Mäkelä authored
Embedded server does not support restarting and needs to skip the test.
-
Marko Mäkelä authored
if XA PREPARE transactions hold explicit locks. innobase_shutdown_for_mysql(): Call trx_sys_close() before lock_sys_close() (and dict_close()) so that trx_free_prepared() will see all locks intact. RB: 8561 Reviewed-by: Vasil Dimov <vasil.dimov@oracle.com>
-