1. 16 Apr, 2020 1 commit
  2. 15 Apr, 2020 6 commits
  3. 14 Apr, 2020 2 commits
  4. 13 Apr, 2020 6 commits
  5. 12 Apr, 2020 1 commit
  6. 10 Apr, 2020 1 commit
    • Sergey Vojtovich's avatar
      MDEV-21599 - plugins.server_audit fails sporadically in buildbot · 06219c2a
      Sergey Vojtovich authored
      Fixed a couple of race conditions in the test case to ensure stable order
      of events. Also removed all sleeps. Test execution time is down from 18s
      to 0.15s.
      
      On disconnect audit event is triggered after control is returned to
      mysqltest client. Which means mysqltest may issue more commands
      concurrently before disconnect is actually logged.
      
      Similar problem happens with regular query execution: an event is
      triggered after control is returner to the client. Which may end
      up with unstable order of events in different connections.
      
      Delayed insert rows are enqueued separately and can either be combined
      into single event or go as separate events. Reduced number of inserted
      rows to 1 to stabilize result.
      
      Also backported 2b3f6ab4 from 10.5.
      06219c2a
  7. 08 Apr, 2020 5 commits
  8. 07 Apr, 2020 2 commits
    • Vlad Lesin's avatar
      MDEV-21168: Active XA transactions stop slave from working after backup · 5836191c
      Vlad Lesin authored
      was restored.
      
      Optionally rollback prepared XA's on "mariabackup --prepare".
      
      The fix MUST NOT be ported on 10.5+, as MDEV-742 fix solves the issue for
      slaves.
      5836191c
    • Rasmus Johansson's avatar
      MDEV-22176 Add JUnit support to MTR to generate XML test result · 5720db2b
      Rasmus Johansson authored
      A new parameter has been added called xml-report, with which the
      filename of the XML file is given to which the XML result is
      written. There is also xml-package for adding a package value in
      the XML output. Example usage:
      ./mysql-test-run.pl main.events_bugs innodb.count_distinct
      main.explain_json innodb.file_format_defaults json.json_no_table
      --suite=main,innodb,json --force --xml-report=build123456789.xml
      --xml-package=simpletestrun
      5720db2b
  9. 06 Apr, 2020 2 commits
  10. 05 Apr, 2020 3 commits
  11. 04 Apr, 2020 1 commit
    • Igor Babaev's avatar
      MDEV-21673 Calling stored procedure twice in the same session causes MariaDB to crash · 21b87437
      Igor Babaev authored
      This bug could happen only with a stored procedure containing queries with
      more than one reference to a CTE that used local variables / parameters.
      
      This bug was the result of an incomplete merge of the fix for the bug
      MDEV-17154. The merge covered usage of parameter markers occurred in a CTE
      that was referenced more than once, but missed coverage of local variables.
      21b87437
  12. 03 Apr, 2020 6 commits
  13. 02 Apr, 2020 4 commits
    • Aleksey Midenkov's avatar
      MDEV-20515 multi-update tries to position updated table by null reference · 0932c580
      Aleksey Midenkov authored
      Cause
      
      Join tmp table inserts null row because of OUTER JOIN, that's
      expected. Since `multi_update::prepare2()` converted
      `Item_temptable_rowid` into `Item_field` (28dbdf3d)
      `multi_update::send_data()` accesses join tmp record directly and
      treats it as a normal row ignoring null status of ref field. NULL ref
      field is then treated as normal in `multi_update::do_updates()` which
      tries to position updated table by reference 0.
      
      Note that reference 0 may be valid reference and the first row of
      table can be wrongly updated (see multi_update.test).
      
      Fix
      
      Do not add row into multi-update tmp table in case of null ref
      field. Join tmp table does not have null_row status at this time (as
      well as `STATUS_NULL_ROW`) and cannot be skipped by these properties
      (see first comment in multi_update::send_data()). But it has all null
      fields (including the ref field).
      0932c580
    • Aleksey Midenkov's avatar
      MDEV-21688 Assertion or ER_WARN_DATA_OUT_OF_RANGE upon ALTER on previously versioned table · ba34f409
      Aleksey Midenkov authored
      Earlier skip of history row. Cleanup of dead code for VTMD.
      ba34f409
    • Aleksey Midenkov's avatar
      MDEV-21342 Assertion in set_ok_status() upon spatial field error on system-versioned table · 44c6c7a9
      Aleksey Midenkov authored
      SQL_SELECT::check_quick() returns error status only
      test_quick_select() returns -1. Fix error handling when lower frames
      throw error, but it is ignored by test_quick_select(). Fix return
      status for out-of-memory errors which are obviously must be processed
      as error in upper frames.
      44c6c7a9
    • Nikita Malyavin's avatar
      MDEV-17091 - Assertion failed after dropping versioning · 9149017b
      Nikita Malyavin authored
      Assertion `old_part_id == m_last_part' failed in ha_partition::update_row or `part_id == m_last_part' in ha_partition::delete_row upon UPDATE/DELETE after dropping versioning
      
      PRIMARY KEY change hadn't been treated as partition reorganization in case of partitioning by KEY() (without parameters).
      
      * set `*partition_changed= true` in the described case.
      * since add/drop system versioning does not affect alter_info->key_list, it required separate attention
      9149017b