1. 07 Jul, 2017 9 commits
  2. 06 Jul, 2017 11 commits
    • Marko Mäkelä's avatar
      Reduce a test so that it fails less frequently on buildbot · c89c4942
      Marko Mäkelä authored
      There is an inherent race condition between Mariabackup and the
      MariaDB server when the InnoDB redo log is being copied. It is
      possible that the tail of the circular redo log is overwriting
      the head of the log before Mariabackup gets a chance to read it.
      So, we reduce the test to generate less redo log. Also, enable
      the test on all supported innodb_page_size.
      c89c4942
    • Marko Mäkelä's avatar
      Merge 10.1 into 10.2 · d902d43c
      Marko Mäkelä authored
      d902d43c
    • Marko Mäkelä's avatar
      Mariabackup: Copy all of the redo log correctly · 99d52c45
      Marko Mäkelä authored
      xtrabackup_copy_log(), xtrabackup_copy_logfile():
      Change the Boolean parameter to an enum, with the values
      COPY_FIRST, COPY_ONLINE, COPY_LAST.
      
      xtrabackup_copy_log(): Return the latest scanned LSN,
      which may be less than the last copied LSN. Remove some
      dead code that was duplicating some logic that in 10.2
      has been moved to log_group_read_log_seg().
      
      log_copying_thread(): Correct the termination condition.
      
      stop_backup_threads(): Shut down the threads that were
      created during backup.
      99d52c45
    • Marko Mäkelä's avatar
      Mariabackup: Remove unused parameters and fix some memory leaks · d7b21a49
      Marko Mäkelä authored
      Use GET_STR instead of GET_STR_ALLOC, so that the memory will
      cannot be leaked. For some reason, calling my_cleanup_options()
      on xb_server_options or xb_client_options would not work.
      d7b21a49
    • Vladislav Vaintroub's avatar
      mysqltest - increase size of the "die message". · 60e61708
      Vladislav Vaintroub authored
      This reduces the probability having output of external utilities
      (e.g mariabackup) truncated.
      60e61708
    • Vladislav Vaintroub's avatar
      MDEV-12445 : Rocksdb does not shutdown worker threads and aborts in memleak... · 6f1f9114
      Vladislav Vaintroub authored
      MDEV-12445 : Rocksdb does not shutdown worker threads and aborts in memleak check on server shutdown
      
      Disable memory leak check in debug server, if rocksdb is loaded.
      There is some subtle bug somewhere in 3rd party code we cannot
      do much about.
      
      The bug is manifested as follows
      
      Rocksdb does not shutdown worker threads, when plugin is shut down. Thus
      OS does not unload the library since there are some active threads using
      this library's code. Thus global destructors in the library do not run,
      and there is still some memory allocated when server exits.
      
      The workaround disables server's memory leak check, if rocksdb engine was
      loaded.
      6f1f9114
    • Vladislav Vaintroub's avatar
      Fix assertion in rocksb. · 53d6325d
      Vladislav Vaintroub authored
      Use thd_query_safe() to read query from a different connection.
      53d6325d
    • Marko Mäkelä's avatar
      MDEV-13247 innodb_log_compressed_pages=OFF breaks crash recovery of ROW_FORMAT=COMPRESSED tables · 2b5c9bc2
      Marko Mäkelä authored
      The option innodb_log_compressed_pages was contributed by
      Facebook to MySQL 5.6. It was disabled in the 5.6.10 GA release
      due to problems that were fixed in 5.6.11, which is when the
      option was enabled.
      
      The option was set to innodb_log_compressed_pages=ON by default
      (disabling the feature), because safety was considered more
      important than speed. The option innodb_log_compressed_pages=OFF
      can *CORRUPT* ROW_FORMAT=COMPRESSED tables on crash recovery
      if the zlib deflate function is behaving differently (producing
      a different amount of compressed data) from how it behaved
      when the redo log records were written (prior to the crash recovery).
      
      In MDEV-6935, the default value was changed to
      innodb_log_compressed_pages=OFF. This is inherently unsafe, because
      there are very many different environments where MariaDB can be
      running, using different zlib versions. While zlib can decompress
      data just fine, there are no guarantees that different versions will
      always compress the same data to the exactly same size. To avoid
      problems related to zlib upgrades or version mismatch, we must
      use a safe default setting.
      
      This will reduce the write performance for users of
      ROW_FORMAT=COMPRESSED tables. If you configure
      innodb_log_compressed_pages=ON, please make sure that you will
      always cleanly shut down InnoDB before upgrading the server
      or zlib.
      2b5c9bc2
    • Monty's avatar
      MDEV-13020 Server crashes in Item_func_nextval::val_int... · 3f327432
      Monty authored
      The problem was that we didn't check on open of sequence if the table is a view, which is not allowed.
      We are now generating a proper error message for this case.
      3f327432
    • Sergey Vojtovich's avatar
      Fixed build failure on Windows · 4e08cdf5
      Sergey Vojtovich authored
      4e08cdf5
    • Fredrik Fornwall's avatar
      Remove obsolete synonyms for access bits · 7e6a600d
      Fredrik Fornwall authored
      Replace S_IREAD, S_IWRITE and S_IEXEC with more modern equivalents.
      Fixes building for Android.
      7e6a600d
  3. 05 Jul, 2017 20 commits