1. 26 May, 2015 1 commit
    • Alexander Barkov's avatar
      A helper patch for "MDEV-8228 Move Item_func_like out of Item_bool_func2" · 5bd25a9c
      Alexander Barkov authored
      - Changing Comp_creator::create() and create_swap() to return
        Item_bool_rowready_func2 instead of Item_bool_func2, as they
        can never return neither Item_func_like nor Item_func_xor
      
      - Changing the first argument of Comp_create::create() and create_swap()
        from THD to MEM_ROOT, so the method implementations can now reside in
        item_cmpfunc.h instead of item_cmpfunc.cc and thus make the code slightly
        easier to read.
      5bd25a9c
  2. 25 May, 2015 1 commit
  3. 21 May, 2015 3 commits
  4. 20 May, 2015 5 commits
    • Jan Lindström's avatar
      MDEV-8182: Failing assertion: 1 == UT_LIST_GET_LEN(space->chain) · 925b6412
      Jan Lindström authored
      Analysis: At fil_spage_get_space there is small change that space
      is found from tablespace list but we have not yet created node
      for it (and added it to space->chain) and as we hold fil_system
      mutex here fil_node_create can't continue.
      
      Fixed by allowing UT_LIST_GET_LEN(space->chain) == 0|| 1 and
      introducint two new functions that access filespace list
      and before returning space check that node is also created.
      925b6412
    • Jan Lindström's avatar
      MDEV-8173: InnoDB; Failing assertion: crypt_data->type == 1 · 3e55ef26
      Jan Lindström authored
      Make sure that when we publish the crypt_data we access the
      memory cache of the tablespace crypt_data. Make sure that
      crypt_data is stored whenever it is really needed.
      
      All this is not yet enough in my opinion because:
      
      sql/encryption.cc has DBUG_ASSERT(scheme->type == 1) i.e.
      crypt_data->type == CRYPT_SCHEME_1
      
      However, for InnoDB point of view we have global crypt_data
      for every tablespace. When we change variables on crypt_data
      we take mutex. However, when we use crypt_data for
      encryption/decryption we use pointer to this global
      structure and no mutex to protect against changes on
      crypt_data.
      
      Tablespace encryption starts in fil_crypt_start_encrypting_space
      from crypt_data that has crypt_data->type = CRYPT_SCHEME_UNENCRYPTED
      and later we write page 0 CRYPT_SCHEME_1 and finally whe publish
      that to memory cache.
      3e55ef26
    • Oleksandr Byelkin's avatar
      MDEV-7921: main.sp_sync fails in buildbot with valgrind · 44cd6f22
      Oleksandr Byelkin authored
      Part 2: detauch service thread.
      44cd6f22
    • Oleksandr Byelkin's avatar
      MDEV-7921: main.sp_sync fails in buildbot with valgrind · c1fb91ef
      Oleksandr Byelkin authored
      Part 1: first 2 cases of valgrind complain. context_analysis_only can be used on non-started LEX (opening tables)
      
      obviouse fixes in DBUG and is_lex_started assignment.
      c1fb91ef
    • Jan Lindström's avatar
  5. 19 May, 2015 3 commits
  6. 18 May, 2015 1 commit
    • Jan Lindström's avatar
      MDEV-8164: Server crashes in pfs_mutex_enter_func after fil_crypt_is_closing or alike · 20c23048
      Jan Lindström authored
      Analysis: Problem was that tablespaces not encrypted might not have
      crypt_data stored on disk.
      
      Fixed by always creating crypt_data to memory cache of the tablespace.
      
      MDEV-8138: strange results from encrypt-and-grep test
      
      Analysis: crypt_data->type is not updated correctly on memory
      cache. This caused problem with state tranfer on
      encrypted => unencrypted => encrypted.
      
      Fixed by updating memory cache of crypt_data->type correctly based on
      current srv_encrypt_tables value to either CRYPT_SCHEME_1 or
      CRYPT_SCHEME_UNENCRYPTED.
      20c23048
  7. 16 May, 2015 2 commits
    • Sergei Golubchik's avatar
      update big tokudb test results after dd8f9319 · 476dfb16
      Sergei Golubchik authored
      that is, after
      
        commit dd8f9319
        Author: Sergei Golubchik <serg@mariadb.org>
        Date:   Fri Apr 10 02:36:54 2015 +0200
      
          be less annoying about sysvar-based table attributes
          do not *always* add them to the create table definition,
          but only when a sysvar value is different from a default.
          also, when adding them - don't quote numbers
      476dfb16
    • Sergei Golubchik's avatar
      upate test results after 2300fe2e · 9cc7eb32
      Sergei Golubchik authored
      that is, after
      
        commit 2300fe2e
        Author: Sergei Golubchik <serg@mariadb.org>
        Date:   Wed May 13 21:57:24 2015 +0200
      
            Identical key derivation code in XtraDB/InnoDB/Aria
      9cc7eb32
  8. 15 May, 2015 7 commits
  9. 14 May, 2015 4 commits
  10. 13 May, 2015 13 commits