1. 24 Aug, 2007 6 commits
  2. 23 Aug, 2007 2 commits
  3. 22 Aug, 2007 3 commits
    • joerg@trift2.'s avatar
      Cleanup in the "netware" subdirectory: · 18b8e7a3
      joerg@trift2. authored
      1) We do not provide the "isam" table handler in 5.0 and up (different from "myisam" !),
         so we do not need the ".def" files for the "isam"-specific tools.
      
      2) Use "basename" to get the base name of a file, not a harder-to-read sed expression.
      18b8e7a3
    • gshchepa/uchum@gleb.loc's avatar
      Merge gleb.loc:/home/uchum/work/bk/5.0-opt-30201 · 16e0a4de
      gshchepa/uchum@gleb.loc authored
      into  gleb.loc:/home/uchum/work/bk/5.0-opt
      16e0a4de
    • gshchepa/uchum@gleb.loc's avatar
      Fixed bug #30201. · f3d0f62d
      gshchepa/uchum@gleb.loc authored
      Killing a SELECT query with KILL QUERY or KILL CONNECTION
      causes a server crash if the query cache is enabled.
      
      Normal evaluation of a query may be interrupted by the
      KILL QUERY/CONNECTION statement, in this case the mysql_execute_command
      function returns TRUE, and the thd->killed flag has true value.
      In this case the result of the query may
      be cached incompletely (omitting call to query_cache_insert inside
      the net_real_write function), and next call to query_cache_end_of_result
      may lead to server crash.
      Thus, the query_cache_end_of_result function has been modified to abort
      query cache in the case of killed thread.
      f3d0f62d
  4. 21 Aug, 2007 9 commits
  5. 20 Aug, 2007 4 commits
  6. 18 Aug, 2007 1 commit
  7. 17 Aug, 2007 3 commits
  8. 16 Aug, 2007 3 commits
  9. 15 Aug, 2007 9 commits
    • tsmith@ramayana.hindu.god's avatar
      NULL MERGE this ChangeSet to 5.1 · 5e926bc1
      tsmith@ramayana.hindu.god authored
      Apply innodb-5.0-ss1696 snapshot
      
      Fixes:
      - Bug#20090: InnoDB: Error: trying to declare trx to enter InnoDB
      - Bug#23710: crash_commit_before fails if innodb_file_per_table=1
        At InnoDB startup consider the case where log scan went beyond
        checkpoint_lsn as a crash and initiate crash recovery code path.
      - Bug#28781: InnoDB increments auto-increment value incorrectly with ON DUPLICATE KEY UPDATE
        We need to do some special AUTOINC handling for the following case:
        INSERT INTO t (c1,c2) VALUES(x,y) ON DUPLICATE KEY UPDATE ...
        We need to use the AUTOINC counter that was actually used by
        MySQL in the UPDATE statement, which can be different from the
        value used in the INSERT statement.
      - Bug#29097: fsp_get_available_space_in_free_extents() is capped at 4TB
        Fix by typecasting the variables before multiplying them, so that the
        result of the multiplication is of type "unsigned long long".
      - Bug#29155: Innodb "Parallel recovery" is not prevented
        Fix by enabling file locking on FreeBSD.  It has been disabled because
        InnoDB has refused to start on FreeBSD & LinuxThreads, but now it
        starts just fine.
      5e926bc1
    • tsmith@ramayana.hindu.god's avatar
      Merge ramayana.hindu.god:/home/tsmith/m/bk/50 · e2d64f28
      tsmith@ramayana.hindu.god authored
      into  ramayana.hindu.god:/home/tsmith/m/bk/maint/50
      e2d64f28
    • davi@moksha.local's avatar
    • lars/lthalmann@dl145h.mysql.com's avatar
      Merge mysql.com:/nfsdisk1/lars/MERGE/mysql-4.1-merge · 04981779
      lars/lthalmann@dl145h.mysql.com authored
      into  mysql.com:/nfsdisk1/lars/MERGE/mysql-5.0-merge
      04981779
    • lars/lthalmann@dl145k.mysql.com's avatar
      Merge mysql.com:/nfsdisk1/lars/bkroot/mysql-5.0-rpl · 4000c96a
      lars/lthalmann@dl145k.mysql.com authored
      into  mysql.com:/nfsdisk1/lars/MERGE/mysql-5.0-merge
      4000c96a
    • lars/lthalmann@mysql.com/dl145k.mysql.com's avatar
      Merge mysql.com:/nfsdisk1/lars/bkroot/mysql-4.1-rpl · 75925a19
      into  mysql.com:/nfsdisk1/lars/MERGE/mysql-4.1-merge
      75925a19
    • igor@olga.mysql.com's avatar
      Fixed bug #30396. · d790ec42
      igor@olga.mysql.com authored
      The bug caused memory corruption for some queries with top OR level
      in the WHERE condition if they contained equality predicates and 
      other sargable predicates in disjunctive parts of the condition.
      
      The corruption happened because the upper bound of the memory
      allocated for KEY_FIELD and SARGABLE_PARAM internal structures
      containing info about potential lookup keys was calculated incorrectly
      in some cases. In particular it was calculated incorrectly when the
      WHERE condition was an OR formula with disjuncts being AND formulas
      including equalities and other sargable predicates.
      d790ec42
    • davi@moksha.local's avatar
      Bug#25856 (HANDLER table OPEN in one connection lock DROP TABLE in another one) · c290b26c
      davi@moksha.local authored
      mysql_ha_open calls mysql_ha_close on the error path (unsupported) to close the (opened) table before inserting it into the tables hash list handler_tables_hash) but mysql_ha_close only closes tables which are on the hash list, causing the table to be left open and locked.
      
      This change moves the table close logic into a separate function that is always called on the error path of mysql_ha_open or on a normal handler close (mysql_ha_close).
      c290b26c
    • evgen@moonbone.local's avatar
      mysql_client_test.c: · 222fddcb
      evgen@moonbone.local authored
        Post fix for the bug#29948.
      222fddcb