1. 08 Mar, 2017 6 commits
  2. 06 Mar, 2017 1 commit
  3. 05 Mar, 2017 1 commit
  4. 03 Mar, 2017 1 commit
    • Marko Mäkelä's avatar
      MDEV-11520: Retry posix_fallocate() after EINTR. · 6b8173b6
      Marko Mäkelä authored
      The function posix_fallocate() as well as the Linux system call
      fallocate() can return EINTR when the operation was interrupted
      by a signal. In that case, keep retrying the operation, except
      if InnoDB shutdown has been initiated.
      6b8173b6
  5. 28 Feb, 2017 1 commit
  6. 27 Feb, 2017 23 commits
  7. 24 Feb, 2017 1 commit
    • Igor Babaev's avatar
      Fixed bug mdev-7992. · ac78927a
      Igor Babaev authored
      'Not exists' optimization can be used for nested outer joins
      only if IS NULL predicate from the WHERE condition is activated.
      So we have to check that all guards that wrap this predicate
      are in the 'open' state.
      This patch supports usage of 'Not exists' optimization for any
      outer join, no matter how it's nested in other outer joins.
      
      This patch is also considered as a proper fix for bugs
      #49322/#58490 and LP #817360.
      ac78927a
  8. 23 Feb, 2017 1 commit
  9. 22 Feb, 2017 3 commits
    • Marko Mäkelä's avatar
      MDEV-11520/MDEV-5746 post-fix: Do not posix_fallocate() too much. · 365c4e97
      Marko Mäkelä authored
      Before the MDEV-11520 fixes, fil_extend_space_to_desired_size()
      in MariaDB Server 5.5 incorrectly passed the desired file size as the
      third argument to posix_fallocate(), even though the length of the
      extension should have been passed. This looks like a regression
      that was introduced in the 5.5 version of MDEV-5746.
      365c4e97
    • Marko Mäkelä's avatar
      MDEV-11520 post-fixes · 6de50b2c
      Marko Mäkelä authored
      Remove the unused variable desired_size.
      
      Also, correct the expression for the posix_fallocate() start_offset,
      and actually test that it works with a multi-file system tablespace.
      Before MDEV-11520, the expression was wrong in both innodb_plugin and
      xtradb, in different ways.
      
      The start_offset formula was tested with the following:
      
      ./mtr --big-test --mysqld=--innodb-use-fallocate \
      --mysqld=--innodb-data-file-path='ibdata1:5M;ibdata2:5M:autoextend' \
      --parallel=auto --force --retry=0 --suite=innodb &
      
      ls -lsh mysql-test/var/*/mysqld.1/data/ibdata2
      6de50b2c
    • Sachin Setiya's avatar
      MDEV-11718 5.5 rpl and federated tests massively fail in buildbot with valgrind · 32591b75
      Sachin Setiya authored
      Problem:- When MariaDB is compiled with jemalloc support, And we run mtr valgrind
      test, valgrind interferes with libjemalloc and returns false errors.
      
      Solution:- Run valgrind with --soname-synonyms=somalloc=libjemalloc* or
      --soname-synonyms=somalloc=NONE depending on whether we are dynamically
      linking or statically linking.
      Signed-off-by: default avatarSachin Setiya <sachin.setiya@mariadb.com>
      32591b75
  10. 21 Feb, 2017 2 commits
    • Alexey Botchkov's avatar
      MDEV-10418 Assertion `m_extra_cache' failed in · cf673ade
      Alexey Botchkov authored
      ha_partition::late_extra_cache(uint).
      
              m_extra_prepare_for_update should be cleaned in
              ha_partition::reset()
      cf673ade
    • Marko Mäkelä's avatar
      MDEV-11520 Extending an InnoDB data file unnecessarily allocates · 978179a9
      Marko Mäkelä authored
      a large memory buffer on Windows
      
      fil_extend_space_to_desired_size(), os_file_set_size(): Use calloc()
      for memory allocation, and handle failures. Properly check the return
      status of posix_fallocate().
      
      On Windows, instead of extending the file by at most 1 megabyte at a time,
      write a zero-filled page at the end of the file.
      According to the Microsoft blog post
      https://blogs.msdn.microsoft.com/oldnewthing/20110922-00/?p=9573
      this will physically extend the file by writing zero bytes.
      (InnoDB never uses DeviceIoControl() to set the file sparse.)
      
      For innodb_plugin, port the XtraDB fix for MySQL Bug#56433
      (introducing fil_system->file_extend_mutex). The bug was
      fixed differently in MySQL 5.6 (and MariaDB Server 10.0).
      978179a9