1. 11 May, 2020 2 commits
    • Daniel Bartholomew's avatar
      bump the VERSION · 37759b26
      Daniel Bartholomew authored
      37759b26
    • Marko Mäkelä's avatar
      MDEV-22523 index->rtr_ssn.mutex is wasting memory · ba3d58ad
      Marko Mäkelä authored
      As part of the SPATIAL INDEX implementation in InnoDB,
      dict_index_t was expanded by a rtr_ssn_t field. There are only
      3 operations for this field, all protected by rtr_ssn_t::mutex:
      
      * btr_cur_search_to_nth_level() stores the least significant 32 bits
      of the 64-bit value that is stored in the index root page.
      (This would better be done when the table is opened for the
      very first time.)
      * rtr_get_new_ssn_id() increments the value by 1.
      * rtr_get_current_ssn_id() reads the current value.
      
      All these operations can be implemented equally safely by using
      atomic memory access operations.
      ba3d58ad
  2. 09 May, 2020 1 commit
  3. 08 May, 2020 4 commits
  4. 07 May, 2020 1 commit
    • Marko Mäkelä's avatar
      MDEV-19344 innodb.innodb-change-buffer-recovery fails · 0dee57c6
      Marko Mäkelä authored
      The test was incompatible with ./mtr --repeat=2 until
      commit 2d6719d7
      fixed that.
      
      It turns out that the failing assertion that we disabled in
      commit 3db94d24
      is bogus and can fail when the change buffer is emptied
      during the last batch of crash recovery. The reason for this
      is the condition around the page_create_empty() call in
      page_cur_delete_rec(). The condition was removed in MariaDB
      Server 10.5 as part of MDEV-12353, in
      commit 7ae21b18 and
      commit f8a9f906.
      
      The bug that the assertion aimed to catch is MDEV-22497, which
      was fixed in commit 26aab96e.
      0dee57c6
  5. 06 May, 2020 2 commits
  6. 05 May, 2020 2 commits
    • Varun Gupta's avatar
      MDEV-13266: Race condition in ANALYZE TABLE / statistics collection · 06b245f7
      Varun Gupta authored
      Fixing a race condition while collecting the engine independent statistics.
      
      Thread1>
      1) start running "ANALYZE TABLE t PERISTENT FOR COLUMNS (..) INDEXES ($list)"
      2) Walk through $list and save it in TABLE::keys_in_use_for_query
      3) Close/re-open tables
      
      Thread2>
      1) Make some use of table t. This involves taking table t from
         the table cache, and putting it back (with TABLE::keys_in_use_for_query reset to 0)
      
      Thread1>
      continue collecting EITS stats. Since TABLE::keys_in_use_for_query is set to 0 we
      will not collect statistics for indexes in $list.
      06b245f7
    • Marko Mäkelä's avatar
      MDEV-11254 cleanup: Remove buf_page_t::write_size · b9f177f6
      Marko Mäkelä authored
      commit 6495806e removed all reads
      of buf_page_t::write_size. Let us remove the field altogether.
      b9f177f6
  7. 04 May, 2020 6 commits
  8. 02 May, 2020 2 commits
  9. 30 Apr, 2020 12 commits
  10. 29 Apr, 2020 8 commits