1. 10 Feb, 2022 16 commits
  2. 09 Feb, 2022 2 commits
  3. 08 Feb, 2022 2 commits
  4. 07 Feb, 2022 1 commit
  5. 06 Feb, 2022 3 commits
  6. 05 Feb, 2022 4 commits
  7. 04 Feb, 2022 10 commits
  8. 03 Feb, 2022 2 commits
    • Marko Mäkelä's avatar
      MDEV-27058 fixup: Crash in innodb.leaf_page_corrupted_during_recovery · 82f5981e
      Marko Mäkelä authored
      buf_page_get_low(): If the page was read-fixed, validate the page ID
      because the page could have been marked as corrupted. We should retry
      the page read in this case, instead of returning a soon-to-be-evicted
      corrupted page to the caller.
      
      This was initially only observed on Microsoft Windows.
      On Linux, this was repeated after adding a sleep
      to buf_pool_t::corrupted_evict() between
      bpage->zip.fix.fetch_sub() and bpage->lock.x_unlock().
      82f5981e
    • Marko Mäkelä's avatar
      MDEV-27736 Allow seamless upgrade despite ROW_FORMAT=COMPRESSED · 05c33d62
      Marko Mäkelä authored
      In commit 9bc874a5 (MDEV-23497)
      the configuration option innodb_read_only_compressed was introduced
      to giver users advance notice of a plan to remove ROW_FORMAT=COMPRESSED
      support for InnoDB.
      
      Based on user feedback, this plan has been scrapped.
      Even though ROW_FORMAT=COMPRESSED is a dead end and causes some
      overhead for InnoDB data structures, we can live with that.
      
      Now that we know that some users really want to keep using
      ROW_FORMAT=COMPRESSED, the previous default value of the parameter
      innodb_read_only_compressed=ON should be changed to OFF, to allow
      smooth upgrades to 10.6 and later versions, without requiring users
      to update any configuration file.
      05c33d62