1. 14 Jan, 2019 1 commit
    • Marko Mäkelä's avatar
      MDEV-18224 MTR's internal check of the test case 'innodb.recovery_shutdown'... · 69290ce3
      Marko Mäkelä authored
      MDEV-18224 MTR's internal check of the test case 'innodb.recovery_shutdown' failed due to extra #sql-ib*.ibd files
      
      The test innodb.recovery_shutdown would occasionally fail,
      because recovered incomplete transactions would be conflicting
      with DROP TABLE, causing the background drop table queue to be invoked.
      
      Add a slow shutdown before dropping the tables, so that the
      recovered transactions will be rolled back. Starting with MDEV-14705,
      normal shutdown would abort the rollback of recovered transactions.
      69290ce3
  2. 10 Jan, 2019 2 commits
  3. 09 Jan, 2019 2 commits
  4. 08 Jan, 2019 3 commits
  5. 07 Jan, 2019 1 commit
  6. 06 Jan, 2019 1 commit
  7. 04 Jan, 2019 7 commits
  8. 03 Jan, 2019 8 commits
    • Marko Mäkelä's avatar
      Fix a merge error in the parent commit · 23e4446a
      Marko Mäkelä authored
      Fix an inadvertently inverted condition that caused
      galera.galera_sst_mariabackup_table_options test failure.
      23e4446a
    • Marko Mäkelä's avatar
      Merge 10.2 into 10.3 · 94e22efb
      Marko Mäkelä authored
      94e22efb
    • Marko Mäkelä's avatar
      Merge 10.1 into 10.2 · b7392d14
      Marko Mäkelä authored
      b7392d14
    • Marko Mäkelä's avatar
      MDEV-18129 Backup fails for encrypted tables: mariabackup: Database page... · 7158edcb
      Marko Mäkelä authored
      MDEV-18129 Backup fails for encrypted tables: mariabackup: Database page corruption detected at page 1
      
      If an encrypted table is created during backup, then
      mariabackup --backup could wrongly fail.
      
      This caused a failure of the test mariabackup.huge_lsn once on buildbot.
      
      This is due to the way how InnoDB creates .ibd files. It would first
      write a dummy page 0 with no encryption information. Due to this,
      xb_fil_cur_open() could wrongly interpret that the table is not encrypted.
      Subsequently, page_is_corrupted() would compare the computed page
      checksum to the wrong checksum. (There are both "before" and "after"
      checksums for encrypted pages.)
      
      To work around this problem, we introduce a Boolean option
      --backup-encrypted that is enabled by default. With this option,
      Mariabackup will assume that a nonzero key_version implies that the
      page is encrypted. We need this option in order to be able to copy
      encrypted tables from MariaDB 10.1 or 10.2, because unencrypted pages
      that were originally created before MySQL 5.1.48 could contain nonzero
      garbage in the fields that were repurposed for encryption.
      
      Later, MDEV-18128 would clean up the way how .ibd files are created,
      to remove the need for this option.
      
      page_is_corrupted(): Add missing const qualifiers, and do not check
      space->crypt_data unless --skip-backup-encrypted has been specified.
      
      xb_fil_cur_read(): After a failed page read, output a page dump.
      7158edcb
    • Sergei Golubchik's avatar
      "fix" sequence.temporary test · 8cbb0bfa
      Sergei Golubchik authored
      8cbb0bfa
    • Sergei Golubchik's avatar
      Merge branch '10.2' into 10.3 · 6bb11efa
      Sergei Golubchik authored
      6bb11efa
    • Sergei Golubchik's avatar
      Merge branch '10.1' into 10.2 · 842402e4
      Sergei Golubchik authored
      842402e4
    • Sergei Golubchik's avatar
      Merge branch '10.0' into 10.1 · 3ba3f81a
      Sergei Golubchik authored
      3ba3f81a
  9. 02 Jan, 2019 9 commits
  10. 30 Dec, 2018 1 commit
  11. 29 Dec, 2018 5 commits