1. 22 Jun, 2016 1 commit
  2. 21 Jun, 2016 12 commits
  3. 20 Jun, 2016 7 commits
    • Jan Lindström's avatar
      Merge commit from 10.1: · c3c4d55e
      Jan Lindström authored
      commit 4165961d
      Author:	Sergei Golubchik <serg@mariadb.org>  Fri Oct 16 02:07:06 2015
      Committer:	Sergei Golubchik <serg@mariadb.org>  Mon Nov 16 08:55:55 2015
      
      disable innodb on sol10-64
      
      because buildbot config invokes BUILD/compile-solaris-amd64
      with the --extra-args=--without-plugin-innodb argument, but
      BUILD/compile-solaris-amd64 doesn't take arguments and doesn't
      invoke configure.pl, so this extra-args is lost.
      c3c4d55e
    • Sergei Golubchik's avatar
      fix a mysql-5.5.50 merge: mysqlcheck · a482e76e
      Sergei Golubchik authored
      quote identifiers correctly
      a482e76e
    • Sergei Golubchik's avatar
      MDEV-9749 InnoDB receives 'Bad file descriptor' error, possibly related to feedback plugin · 95bf696d
      Sergei Golubchik authored
      and
      MDEV-10250 InnoDB: Error: File (unknown): 'close' returned OS error 209. Cannot continue operation"
      
      after a failed connect() feedback plugin was continuing with the
      file descriptor, trying to send the data (which failed) and
      closing it at the end. Even though this fd might've been reused for
      something else already.
      95bf696d
    • Olivier Bertrand's avatar
    • Sergey Vojtovich's avatar
      MDEV-10043 - main.events_restart fails sporadically in buildbot (crashes upon · 7f38a070
      Sergey Vojtovich authored
                   shutdown)
      
      There was race condition between shutdown thread and event worker threads.
      
      Shutdown thread waits for thread_count to become 0 in close_connections(). It
      may happen so that event worker thread was started but didn't increment
      thread_count by this time. In this case shutdown thread may miss wait for this
      working thread and continue deinitialization. Worker thread in turn may continue
      execution and crash on deinitialized data.
      
      Fixed by incrementing thread_count before thread is actually created like it is
      done for connection threads.
      
      Also let event scheduler not to inc/dec running threads counter for symmetry
      with other "service" threads.
      7f38a070
    • Alexander Barkov's avatar
      MDEV-10020 InnoDB NOT IN Query Crash When One Item Is NULL · a80dbe06
      Alexander Barkov authored
      The problem was that the loop in get_func_mm_tree()
      accessed improperly initialized instances of String,
      which resided in the bzero'ed part of the in_vector::base array.
      
      Strings in in_vector::base are originally initialized
      in Item_func_in::fix_length_and_dec(),
      in in_vector::in_vector() using sql_calloc,
      rather than using a String constructor, so their str_charset
      members are originally equal to NULL.
      
      Strings in in_vector::base are later initialized
      to good values in Item_func_in::fix_length_and_dec(),
      using array->set(), in this code:
      
            uint j=0;
            for (uint i=1 ; i < arg_count ; i++)
            {
              array->set(j,args[i]);
              if (!args[i]->null_value)                      // Skip NULL values
                j++;
              else
                have_null= 1;
            }
            if ((array->used_count= j))
              array->sort();
      
      NULLs are not taken into account, so at the end
      array->used_count can be smaller than array->count.
      
      This patch fixes the loop in opt_range.cc, in get_func_mm_tree(),
      to access only properly initialized elements in in_vector::base,
      preventing access to its bzero'ed non-initialized tail.
      a80dbe06
    • Jan Lindström's avatar
      MDEV-8633: information_schema.index_statistics doesn't delete · 70ad689b
      Jan Lindström authored
      item when drop table indexes or drop table;
      
      Problem was that table and index statistics is removed from
      persistent tables but not from memory cache. Added functions
      to remove table and index statistics from memory cache.
      70ad689b
  4. 18 Jun, 2016 1 commit
  5. 17 Jun, 2016 2 commits
  6. 16 Jun, 2016 6 commits
  7. 15 Jun, 2016 1 commit
  8. 14 Jun, 2016 10 commits