An error occurred fetching the project authors.
  1. 27 Jan, 2017 1 commit
    • Marko Mäkelä's avatar
      Clean up a few tests that kill the server. · 0f34160d
      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.
      0f34160d
  2. 15 Jan, 2017 1 commit
    • Marko Mäkelä's avatar
      MDEV-11799 InnoDB can abort if the doublewrite buffer · a9d00db1
      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.
      a9d00db1
  3. 30 Sep, 2016 1 commit
  4. 24 Sep, 2015 1 commit
    • Elena Stepanova's avatar
      MDEV-8841 innodb_zip.innodb-create-options fails in buildbot · dca4ab92
      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
      dca4ab92
  5. 09 Apr, 2015 2 commits