1. 07 Sep, 2017 6 commits
  2. 06 Sep, 2017 9 commits
  3. 05 Sep, 2017 2 commits
  4. 04 Sep, 2017 4 commits
    • andrelkin's avatar
      MDEV-12731 · 8592ff9e
      andrelkin authored
      Was reported as 'rpl.rpl_gtid_stop_start fails with Valgrind in buildbot and outside'.
      The 'Conditional jump or move depends on uninitialized value' valgrind complaint is valid
      and means THD::m_current_stage_key that is not initialized indeed by constructor.
      
      Fixed with its initialization added to the initializer list of
      THD::THD.  Double checked with mysql to have found a similar fixes for
      the very same issue which was discovered after P_S merge to Maria
      (60589aee where the member is introduced) had been done.
      8592ff9e
    • Andrei Elkin's avatar
      Post-push for MDEV-13437 · 641baa5d
      Andrei Elkin authored
      A new $MYSQLD_LAST_CMD evaluation was too late in case --manual-gdb.
      Now it is done before the server restart type branches which is safe
      and the args value has been fully computed by the new point of
      evaluation.
      641baa5d
    • Oleksandr Byelkin's avatar
      MDEV-10972: Insert from select / view / union -- repeatable crash in 10.1, 10.2 Linux/Mac/Windows · 17589989
      Oleksandr Byelkin authored
      save thd->select_number between parsing and executions (in case it was not complete executed due to errors (for example epsent table))
      17589989
    • Marko Mäkelä's avatar
      MDEV-13705 10.0.32 does not compile on architectures without 64-bit atomics · 05008999
      Marko Mäkelä authored
      This is a backport of the following:
      
      MDEV-13009 10.1.24 does not compile on architectures without 64-bit atomics
      
      Add a missing #include "sync0types.h" that was removed in MDEV-12674.
      05008999
  5. 03 Sep, 2017 1 commit
  6. 01 Sep, 2017 4 commits
  7. 31 Aug, 2017 14 commits
    • Marko Mäkelä's avatar
      Merge 10.1 into 10.2 · 5660c061
      Marko Mäkelä authored
      5660c061
    • Marko Mäkelä's avatar
      Merge 10.0 into 10.1 · be45f083
      Marko Mäkelä authored
      be45f083
    • Vladislav Vaintroub's avatar
      MDEV-13693 : Fix parameter passing to my_error. · 6be93c3b
      Vladislav Vaintroub authored
      char* parameter is expected by the message ER_KEY_COLUMN_DOES_NOT_EXITS,
      thus pass char*, rather than LEX_STRING.
      6be93c3b
    • Vladislav Vaintroub's avatar
      MDEV-13691 : my_write() sets inappropriate errno for ERROR_FILE_SYSTEM_LIMITATON · 66eb9774
      Vladislav Vaintroub authored
      ERROR_FILE_SYSTEM_LIMITATION was seen by support when backing up large
      file. However mariabackup error message was not very helpful,
      since it mapped the error to generic catch-all EINVAL.
      
      With the patch, ERROR_FILE_SYSTEM_LIMITATION will be mapped to more
      appropriate EFBIG. Also add mapping from ERROR_NO_SYSTEM_RESOURCES
      to ENOMEM.
      66eb9774
    • Marko Mäkelä's avatar
      Disable a badly written, randomly failing Galera test · a9e71c77
      Marko Mäkelä authored
      CURRENT_TEST: galera.galera_kill_applier
      mysqltest: At line 14: query 'KILL $applier_thread' failed with wrong
      errno 1064: 'You have an error in your SQL syntax; check the manual
      that corresponds to your MariaDB server version for the right syntax
      to use near '' at line 1', instead of 1095...
      a9e71c77
    • Jan Lindström's avatar
      MDEV-13674: Deprecate innodb_use_mtflush and innodb_mtflush_threads · e23de9f2
      Jan Lindström authored
      These parameters and associated code is to be removed in 10.3.
      Users can use innodb-page-cleaners > 1 instead.
      e23de9f2
    • Jan Lindström's avatar
      MDEV-12741: innodb.ibuf_not_empty failed in buildbot with "InnoDB: Trying to... · aa22981d
      Jan Lindström authored
      MDEV-12741: innodb.ibuf_not_empty failed in buildbot with "InnoDB: Trying to do I/O to a tablespace which does not exist"
      
      Background thread is doing ibuf merge, in buf0rea.cc buf_read_ibuf_merge_pages().
      It first tries to get page_size and if space is not found it deletes them, but
      as we do not hold any mutexes, space can be marked as stopped between that
      and buf_read_page_low() for same space. This naturally leads seen error
      message on log.
      
      buf_read_page_low(): Add parameter ignore_missing_space = false that
      is passed to fil_io()
      
      buf_read_ibuf_merge_pages(): call buf_read_page_low with
      ignore_missing_space = true, this function will handle missing
      space error code after buf_read_page_low returns.
      
      fil_io(): if ignore_missing_space = true do not print error
      message about trying to do I/0 for missing space, just return
      correct error code that is handled later.
      aa22981d
    • Sergei Petrunia's avatar
      MDEV-13669: Some MyRocks test take a long time · 0e45edf3
      Sergei Petrunia authored
      Make rocksdb.bloomfilter* tests 1.8x faster by doing loading in bulk
      0e45edf3
    • Marko Mäkelä's avatar
      Merge 10.1 into 10.2 · 2000a900
      Marko Mäkelä authored
      2000a900
    • Marko Mäkelä's avatar
      MDEV-13684 InnoDB race condition between fil_crypt_thread and btr_scrub_init · 38ca9be4
      Marko Mäkelä authored
      There is a race condition in InnoDB startup. A number of
      fil_crypt_thread are created by fil_crypt_threads_init(). These threads
      may call btr_scrub_complete_space() before btr_scrub_init() was called.
      Those too early calls would be accessing an uninitialized scrub_stat_mutex.
      
      innobase_start_or_create_for_mysql(): Invoke btr_scrub_init() before
      fil_crypt_threads_init().
      
      fil_crypt_complete_rotate_space(): Only invoke btr_scrub_complete_space()
      if scrubbing is enabled. There is no need to update the statistics if
      it is not enabled.
      38ca9be4
    • Marko Mäkelä's avatar
      Merge 10.1 into 10.2 · 2f20be94
      Marko Mäkelä authored
      2f20be94
    • Marko Mäkelä's avatar
      Add ATTRIBUTE_NORETURN and ATTRIBUTE_COLD · 4386ee8c
      Marko Mäkelä authored
      ATTRIBUTE_NORETURN is supported on all platforms (MSVS and GCC-like).
      It declares that a function will not return; instead, the thread or
      the whole process will terminate.
      
      ATTRIBUTE_COLD is supported starting with GCC 4.3. It declares that
      a function is supposed to be executed rarely. Rarely used error-handling
      functions and functions that emit messages to the error log should be
      tagged such.
      4386ee8c
    • Marko Mäkelä's avatar
      Fix some badly written Galera tests · 03a8eaa0
      Marko Mäkelä authored
      galera.galera_kill_applier: Make the test less likely to fail
      by adding sleep time.
      
      galera.query_cache: Remove data truncation.
      
      Part of the test file looks like it has been misinterpreted as latin1
      and wrongly converted to UTF-8 encoding. In MariaDB 10.1, the server would
      only warn about data truncation and not issue an error. 10.2 is stricter.
      (The test should be carefully reviewed if it really makes sense.)
      03a8eaa0
    • Marko Mäkelä's avatar
      Merge 10.1 into 10.2 · a36c369b
      Marko Mäkelä authored
      For running the Galera tests, the variable my_disable_leak_check
      was set to true in order to avoid assertions due to memory leaks
      at shutdown.
      
      Some adjustments due to MDEV-13625 (merge InnoDB tests from MySQL 5.6)
      were performed. The most notable behaviour changes from 10.0 and 10.1
      are the following:
      
      * innodb.innodb-table-online: adjustments for the DROP COLUMN
      behaviour change (MDEV-11114, MDEV-13613)
      
      * innodb.innodb-index-online-fk: the removal of a (1,NULL) record
      from the result; originally removed in MySQL 5.7 in the
      Oracle Bug #16244691 fix
      https://github.com/mysql/mysql-server/commit/377774689bf6a16af74182753fe950d514c2c6dd
      
      * innodb.create-index-debug: disabled due to MDEV-13680
      (the MySQL Bug #77497 fix was not merged from 5.6 to 5.7.10)
      
      * innodb.innodb-alter-autoinc: MariaDB 10.2 behaves like MySQL 5.6/5.7,
      while MariaDB 10.0 and 10.1 assign different values when
      auto_increment_increment or auto_increment_offset are used.
      Also MySQL 5.6/5.7 exhibit different behaviour between
      LGORITHM=INPLACE and ALGORITHM=COPY, so something needs to be tested
      and fixed in both MariaDB 10.0 and 10.2.
      
      * innodb.innodb-wl5980-alter: disabled because it would trigger an
      InnoDB assertion failure (MDEV-13668 may need additional effort in 10.2)
      a36c369b