1. 07 Apr, 2006 1 commit
    • kroki@mysql.com's avatar
      Bug#15933: max_used_connections is wrong after FLUSH STATUS if connections are cached · 6222ca41
      kroki@mysql.com authored
      After FLUSH STATUS max_used_connections was reset to 0, and haven't
      been updated while cached threads were reused, until the moment a new
      thread was created.
      
      The first suggested fix from original bug report was implemented:
      
        a) On flushing the status, set max_used_connections to
        threads_connected, not to 0.
      
        b) Check if it is necessary to increment max_used_connections when
        taking a thread from the cache as well as when creating new threads
      6222ca41
  2. 03 Apr, 2006 5 commits
  3. 02 Apr, 2006 1 commit
  4. 01 Apr, 2006 11 commits
  5. 31 Mar, 2006 6 commits
    • kent@mysql.com's avatar
      Makefile.am, yassl.m4: · f5a9cc17
      kent@mysql.com authored
        Enable automake to determine dependency on yaSSL, by explicitly
        listing the .la files in Makefile.am, instead of using
        'yassl_libs_with_path', bug#18273
      f5a9cc17
    • aivanov@mysql.com's avatar
      Merge aivanov@bk-internal.mysql.com:/home/bk/mysql-5.0 · 99f7292b
      aivanov@mysql.com authored
      into  mysql.com:/home/alexi/innodb/mysql-5.0-merged
      99f7292b
    • aivanov@mysql.com's avatar
      Applied innodb-5.0-ss398 snapshot. · 771fb26e
      aivanov@mysql.com authored
       Fixed BUG#15650: DELETE with LEFT JOIN crashes server
       with innodb_locks_unsafe_for_binlog.
       Fixed compilation problem with non-C99 compilers
       in btr0sea.c
      771fb26e
    • timour@mysql.com's avatar
      Fixed a typo. · efdc2fd1
      timour@mysql.com authored
      efdc2fd1
    • timour@mysql.com's avatar
      Merge mysql.com:/home/timka/mysql/src/5.0-virgin · b85bd1e8
      timour@mysql.com authored
      into  mysql.com:/home/timka/mysql/src/5.0-bug-16710
      b85bd1e8
    • timour@mysql.com's avatar
      Fix for BUG#16710. · eed7cf09
      timour@mysql.com authored
      The bug was due to a missed case in the detection of whether an index
      can be used for loose scan. More precisely, the range optimizer chose
      to use loose index scan for queries for which the condition(s) over
      an index key part could not be pushed to the index together with the
      loose scan.
      
      As a result, loose index scan was selecting the first row in the
      index with a given GROUP BY prefix, and was applying the WHERE
      clause after that, while it should have inspected all rows with
      the given prefix, and apply the WHERE clause to all of them.
      
      The fix detects and skips such cases.
      eed7cf09
  6. 30 Mar, 2006 16 commits