1. 27 Sep, 2007 1 commit
  2. 25 Sep, 2007 5 commits
    • mikael@dator6.(none)'s avatar
      Merge dator6.(none):/home/mikael/mysql_clones/mysql-5.1-ndb · b22826fe
      mikael@dator6.(none) authored
      into  dator6.(none):/home/mikael/mysql_clones/bug30996
      b22826fe
    • stewart@willster.(none)'s avatar
      ndb_rand.c: · 5a67e7eb
      stewart@willster.(none) authored
        Rename: ndb/src/common/util/ndb_rand.c -> storage/ndb/src/common/util/ndb_rand.c
      ndb_rand.h:
        Rename: ndb/include/util/ndb_rand.h -> storage/ndb/include/util/ndb_rand.h
      5a67e7eb
    • stewart@willster.(none)'s avatar
      Merge willster.(none):/home/stewart/Documents/MySQL/5.0/ndb · efba7552
      stewart@willster.(none) authored
      into  willster.(none):/home/stewart/Documents/MySQL/5.1/ndb
      efba7552
    • stewart@flamingspork.com[stewart]'s avatar
      [PATCH] BUG#30379 Better randomise time before retry in timeout check (DBTC) · 33412d2b
      stewart@flamingspork.com[stewart] authored
      timoOutLoopStartLab() checks if any transactions have been delayed
      for so long that we are forced to perform some action (e.g. abort,
      resend etc).
      
      It is *MEANT* to (according to the comment):
      > To avoid aborting both transactions in a deadlock detected by time-out
      > we insert a random extra time-out of upto 630 ms by using the lowest
      > six bits of the api connect reference.
      > We spread it out from 0 to 630 ms if base time-out is larger than 3 sec,
      > we spread it out from 0 to 70 ms if base time-out is smaller than 300 msec,
      > and otherwise we spread it out 310 ms.
      
      The comment (as all do) lies.
      
      the API connect reference is not very random, producing incredibly
      predictable "random" numbers. This could lead to both txns being
      aborted instead of just one.
      
      Before:
      timeout value: 123 3
      timeout value: 122 2
      timeout value: 122 2
      timeout value: 122 2
      timeout value: 123 3
      
      After:
      timeout value: 127 7
      timeout value: 126 6
      timeout value: 129 9
      timeout value: 139 19
      timeout value: 137 17
      timeout value: 151 31
      timeout value: 130 10
      timeout value: 132 12
      
      Index: ndb-work/ndb/src/kernel/blocks/dbtc/DbtcMain.cpp
      ===================================================================
      33412d2b
    • mikael@dator6.(none)'s avatar
      Merge dator6.(none):/home/mikael/mysql_clones/mysql-5.1-ndb · c134b5a3
      mikael@dator6.(none) authored
      into  dator6.(none):/home/mikael/mysql_clones/bug30996
      c134b5a3
  3. 19 Sep, 2007 1 commit
  4. 15 Sep, 2007 1 commit
  5. 14 Sep, 2007 2 commits
  6. 13 Sep, 2007 7 commits
  7. 12 Sep, 2007 5 commits
  8. 11 Sep, 2007 3 commits
  9. 09 Sep, 2007 1 commit
    • antony@pcg5ppc.xiphis.org's avatar
      Bug#30919 · 89f88eab
      antony@pcg5ppc.xiphis.org authored
        "Rows not deleted from innodb partitioned tables if --innodb_autoinc_lock_mode=0"
      
        Due to a previous bugfix which initializes a previously uninitialized
        variable, ha_partition::get_auto_increment() may fail to operate
        correctly when the storage engine reports that it is only reserving
        one value and one or more partitions have a different 'next-value'.
        Currently, only affects Innodb's new-style auto-increment code which
        reserves larger blocks of values and has less inter-thread contention.
      89f88eab
  10. 08 Sep, 2007 2 commits
    • acurtis/antony@xiphis.org/ltamd64.xiphis.org's avatar
      perform explicit cleanup · 5558f69d
      add missing opt file
      5558f69d
    • acurtis/antony@xiphis.org/ltamd64.xiphis.org's avatar
      Bug#30907 · d8d199c4
        "Regression: "--innodb_autoinc_lock_mode=0" (off) not same as older releases"
      Bug#28430
        "Failure in replication of innodb partitioned tables on row/mixed format"
      Bug#30888
        "Innodb table + stored procedure + row deletion = server crash"
      
        Apply Oracle patch from Sunny
        Include tests cases by Omer
        Ensure that innobase_read_and_init_auto performs table autoinc lock when lock_mode = 0
        No need for "if" guard around row_unlock_table_autoinc_for_mysql() because
        it already performs same check.
        Make autoinc_lock_mode variable read-only for duration of running mysqld process.
      d8d199c4
  11. 07 Sep, 2007 4 commits
  12. 06 Sep, 2007 2 commits
  13. 05 Sep, 2007 6 commits