1. 21 Nov, 2007 1 commit
  2. 07 Nov, 2007 1 commit
  3. 06 Nov, 2007 2 commits
    • tsmith@ramayana.hindu.god's avatar
      Apply snapshot innodb-5.1-ss2034 · a88d9461
      tsmith@ramayana.hindu.god authored
      The following bugs are fixed:
      
      Bug #31860: Server crashes after inserting into InnoDB table with auto_increment column
        In the Bug 16979 fix there was an erroneous assertion that
        autoincrement columns can't contain negative values. With the fix, the
        autoincrement table counter is set to 0 if the maximum value read from
        the autoinc column index is negative.
      a88d9461
    • tsmith@ramayana.hindu.god's avatar
      Apply snapshot innodb-5.1-ss1989 · eb654791
      tsmith@ramayana.hindu.god authored
      Fixes the following bugs:
      
      Bug #30706: SQL thread on slave is allowed to block client queries when slave load is high
        Add (innodb|innobase|srv)_replication_delay MySQL config parameter.
      
      Bug #30888: Innodb table + stored procedure + row deletion = server crash
        While adding code for the low level read of the AUTOINC value from the index,
        the case for MEDIUM ints which are 3 bytes was missed triggering an
        assertion.
      
      Bug #30907: Regression: "--innodb_autoinc_lock_mode=0" (off) not same as older releases
        We don't rely on *first_value to be 0 when checking whether
        get_auto_increment() has been invoked for the first time in a multi-row
        INSERT. We instead use trx_t::n_autoinc_rows. Initialize trx::n_autoinc_rows
        inside ha_innobase::start_stmt() too.
      
      Bug #31444: "InnoDB: Error: MySQL is freeing a thd" in innodb_mysql.test
        ha_innobase::external_lock(): Update prebuilt->mysql_has_locked and
        trx->n_mysql_tables_in_use only after row_lock_table_for_mysql() returns
        DB_SUCCESS.  A timeout on LOCK TABLES would lead to an inconsistent state,
        which would cause trx_free() to print a warning.
      
      Bug #31494: innodb + 5.1 + read committed crash, assertion
        Set an error code when a deadlock occurs in semi-consistent read.
      eb654791
  4. 05 Nov, 2007 2 commits
  5. 02 Nov, 2007 3 commits
  6. 01 Nov, 2007 3 commits
  7. 31 Oct, 2007 2 commits
  8. 30 Oct, 2007 8 commits
  9. 29 Oct, 2007 12 commits
  10. 26 Oct, 2007 1 commit
    • mleich@four.local.lan's avatar
      Fix for · d3e18cc9
      mleich@four.local.lan authored
         Bug#31408 funcs_1: <engine>_trig_03e test fail
      Modification:
         The TRIGGER PRIVILEGE is now needed for getting informations about TRIGGERs.
         Therefore after REVOKE TRIGGER privilege the 
         - SHOW TRIGGERS
         - SELECT * FROM INFORMATION_SCHEMA.TRIGGERS
         result sets are now empty.
      d3e18cc9
  11. 25 Oct, 2007 4 commits
  12. 24 Oct, 2007 1 commit