1. 06 Mar, 2015 2 commits
    • Sergei Golubchik's avatar
      MDEV-7659 buildbot may leave stale mysqld · 12d87c3b
      Sergei Golubchik authored
      safe_process puts its children (mysqld, in this case) into a separate
      process group, to be able to kill it all at once.
      
      buildslave kills mtr's process group when it loses connection to
      the master.
      
      result? buildslave kills mtr and safe_process, but leaves stale
      mysqld processes in their own process groups.
      
      fix: put safe_process itself into a separate process group, then
      buildslave won't kill it and safe_process will kill mysqld'd
      and itself when it will notice that the parent mtr no longer exists.
      12d87c3b
    • Jan Lindström's avatar
      MDEV-7672: Crash creating an InnoDB table with foreign keys · 206b111b
      Jan Lindström authored
      Analysis: after a red-black-tree lookup we use node withouth
      checking did lookup succeed or not. This lead to situation
      where NULL-pointer was used.
      
      Fix: Add additional check that found node from red-back-tree
      is valid.
      206b111b
  2. 05 Mar, 2015 1 commit
    • Jan Lindström's avatar
      MDEV-7578 :Slave is ~10x slower to execute set of statements compared to master when using RBR · f66fbe8c
      Jan Lindström authored
      Analysis: On master when executing (single/multi) row INSERTs/REPLACEs
      InnoDB fallback to old style autoinc locks (table locks)
      only if another transaction has already acquired the AUTOINC lock.
      Instead on slave as we are executing log_events and sql_command
      is not correctly set, InnoDB does not use new style autoinc
      locks when it could.
      
      Fix: Use new style autoinc locks also when
      thd_sql_command(user_thd) == SQLCOM_END i.e. this is RBR event.
      f66fbe8c
  3. 28 Feb, 2015 1 commit
    • Vicențiu Ciorbaru's avatar
      MDEV-6838: Using too big key for internal temp tables · 45b6edb1
      Vicențiu Ciorbaru authored
      This bug manifests due to wrong computation and evaluation of
      keyinfo->key_length. The issues were:
      * Using table->file->max_key_length() as an absolute value that must not be
        reached for a key, while it represents the maximum number of bytes
        possible for a table key.
      * Incorrectly computing the keyinfo->key_length size during
        KEY_PART_INFO creation. The metadata information regarding the key
        such the field length (for strings) was added twice.
      45b6edb1
  4. 27 Feb, 2015 1 commit
  5. 23 Feb, 2015 1 commit
  6. 13 Feb, 2015 1 commit
  7. 12 Feb, 2015 1 commit
  8. 11 Feb, 2015 5 commits
  9. 10 Feb, 2015 2 commits
  10. 09 Feb, 2015 2 commits
  11. 11 Feb, 2015 1 commit
  12. 10 Feb, 2015 3 commits
  13. 09 Feb, 2015 1 commit
  14. 08 Feb, 2015 2 commits
  15. 06 Feb, 2015 1 commit
  16. 04 Feb, 2015 5 commits
  17. 29 Jan, 2015 1 commit
  18. 28 Jan, 2015 1 commit
  19. 23 Jan, 2015 1 commit
  20. 22 Jan, 2015 2 commits
  21. 21 Jan, 2015 3 commits
  22. 19 Jan, 2015 2 commits