1. 29 Oct, 2009 4 commits
  2. 28 Oct, 2009 4 commits
    • Tor Didriksen's avatar
    • Tor Didriksen's avatar
      Bug#48060 Memory leak - Item::val_bool() (item.cc:184) from optimizer_subquery grammar · b2baeed4
      Tor Didriksen authored
      Item_sum::set_aggregator() may be called multiple times during query preparation.
      On subsequent calls: verify that the aggregator type is the same,
      and re-use the existing Aggregator.
      
      
      sql/item_sum.cc:
        In Item_sum::set_aggregator(): re-use existing Aggregator if already set.
        
        Remove some friend declarations, add some accessor functions.
        Cleanup some DBUG_ENTER and DBUG_RETURN code.
      sql/item_sum.h:
        Make some member fields private, add accessors instead.
        Remove some un-necessary friend declarations.
        Remove some default arguments from constructors.
      sql/opt_sum.cc:
        Use accessor functions in Item_sum.
      sql/sql_select.cc:
        Fix mis-spelled DBUG_ENTER text.
        Use accessor functions in Item_sum.
      sql/sql_yacc.yy:
        Use explicit true/false rather than default arguments when constructing
        Item_sum_xxx objects.
      b2baeed4
    • Alexey Botchkov's avatar
      WL#4991 mysql_upgrade --fix-privilege-tables · 36299d59
      Alexey Botchkov authored
         (backport)
         mysql_upgrade script accepts --upgrade-system-tables option,
         fixing only system tables in this case.
      
      per-file comments:
        client/mysql_upgrade.c
      WL#4991 mysql_upgrade --fix-privilege-tables
          --upgrade-system-tables option added.
         if it is set, the tool won't look for the mysqlcheck then
         run_mysqlcheck_fixnames() and run_mysqlcheck_upgrade won't be called.
        mysql-test/r/mysql_upgrade.result
      WL#4991 mysql_upgrade --fix-privilege-tables
          test result added
        mysql-test/t/mysql_upgrade.test
      WL#4991 mysql_upgrade --fix-privilege-tables
          test case added
      36299d59
    • Alexander Nozdrin's avatar
      Automerge from mysql-next-mr. · 55b8f07a
      Alexander Nozdrin authored
      55b8f07a
  3. 27 Oct, 2009 9 commits
  4. 26 Oct, 2009 4 commits
    • Dmitry Lenev's avatar
      Fix for bug #45143 "All connections hang on concurrent ALTER TABLE". · 86c23fa7
      Dmitry Lenev authored
      Concurrent execution of statements which require non-table-level
      write locks on several instances of the same table (such as
      SELECT ... FOR UPDATE which uses same InnoDB table twice or a DML
      statement which invokes trigger which tries to update same InnoDB
      table directly and through stored function) and statements which
      required table-level locks on this table (e.g. LOCK TABLE ... WRITE,
      ALTER TABLE, ...) might have resulted in a deadlock.
      
      The problem occured when a thread tried to acquire write lock
      (TL_WRITE_ALLOW_WRITE) on the table but had to wait since there was
      a pending write lock (TL_WRITE, TL_WRITE_ALLOW_READ) on this table
      and we failed to detect that this thread already had another instance
      of write lock on it (so in fact we were trying to acquire recursive
      lock) because there was also another thread holding write lock on the
      table (also TL_WRITE_ALLOW_WRITE). When the latter thread released
      its lock neither the first thread nor the thread trying to acquire
      TL_WRITE/TL_WRITE_ALLOW_READ were woken up (as table was still write
      locked by the first thread) so we ended up with a deadlock.
      
      This patch solves this problem by ensuring that thread which
      already has write lock on the table won't wait when it tries
      to acquire second write lock on the same table.
      
      mysql-test/r/lock_sync.result:
        Added test case for bug #45143 "All connections hang on concurrent
        ALTER TABLE".
      mysql-test/t/lock_sync.test:
        Added test case for bug #45143 "All connections hang on concurrent
        ALTER TABLE".
      mysys/thr_lock.c:
        Ensured that thread can acquire write lock on the table without
        waiting if it already has write lock on it even if there are other
        threads holding write locks on this table (this is normal situation
        for, e.g., TL_WRITE_ALLOW_WRITE type of lock).
        
        Adjusted comments to better explain why it is OK to do so and added
        asserts to prevent introduction of scenarios in which this can cause
        problems.
      86c23fa7
    • Vladislav Vaintroub's avatar
      Bug #48317 cannot build innodb as static library. · 1dd88254
      Vladislav Vaintroub authored
      The problem here is that the latest innodb push contains
      both MYSQL_STORAGE_ENGINE(INNOBASE) and MYSQL_STORAGE_ENGINE(INNOBASE)
      in the same CMakeLists.txt, to make the resulting library
      ha_innodb.dll, instead of ha_innobase.dll.
      
      Using multiple MYSQL_STORAGE_ENGINE within the same  CMakeLists.txt
      conflicts with the fix for the bug Bug #47795 "CMake, storage engine
      name different from directory name". Top-level CMakeLists.txt now 
      parses storage engine's  CMakeLists.txt to extract engines name from 
      MYSQL_STORAGE_ENGINE().
      
      For innodb, it concludes that there is not storage engine named
      INNOBASE, hence WITH_INNOBASE_STORAGE_ENGINE has no effect.
      
      The fix is to use SET_TARGET_PROPERTIES(... PROPERTIES OUTPUT_NAME ...),
      instead of renaming the engine to have plugins named ha_innodb.dll.
      1dd88254
    • Alexander Barkov's avatar
    • Sergey Glukhov's avatar
      Bug#35427 INFORMATION_SCHEMA.TABLES.TABLE_CATALOG is NULL, should be "def" · 90e2ad95
      Sergey Glukhov authored
      additional fix(Betony)
      
      90e2ad95
  5. 25 Oct, 2009 1 commit
  6. 23 Oct, 2009 17 commits
  7. 22 Oct, 2009 1 commit