1. 06 Dec, 2007 1 commit
  2. 22 Nov, 2007 1 commit
  3. 14 Nov, 2007 1 commit
  4. 07 Nov, 2007 1 commit
  5. 06 Nov, 2007 1 commit
  6. 05 Nov, 2007 1 commit
    • mskold/marty@mysql.com/quadfish.(none)'s avatar
      ha_ndbcluster.h: · 4cf742a8
        Bug #31956       auto increment bugs in MySQL Cluster: Added utility method and constant for internal prefetch default
      ndb_auto_increment.result:
        BitKeeper file /home/marty/MySQL/mysql-5.0-ndb/mysql-test/r/ndb_auto_increment.result
      mysqld.cc:
        Bug #25176  	Trying to set ndb_autoincrement_prefetch_sz always fails: Changed pointer to max value
        Bug #31956  	auto increment bugs in MySQL Cluster: Changed meaning of ndb_autoincrement_prefetch_sz to specify prefetch between statements, changed default to 1 (with internal prefetch to at least 32 inside a statement)
      ndb_insert.test, ndb_insert.result:
        Moved auto_increment tests to ndb_auto_increment.test
      ndb_auto_increment.test:
        BitKeeper file /home/marty/MySQL/mysql-5.0-ndb/mysql-test/t/ndb_auto_increment.test
      ha_ndbcluster.cc:
        Bug #31956       auto increment bugs in MySQL Cluster: Changed meaning of ndb_autoincrement_prefetch_sz to specify prefetch between statements, changed default to 1 (with internal prefetch to at least 32 inside a statement), added handling of updates of pk/unique key with auto_increment
        Bug #32055  	Cluster does not handle auto inc correctly with insert ignore statement
      4cf742a8
  7. 01 Nov, 2007 1 commit
  8. 26 Oct, 2007 1 commit
  9. 25 Oct, 2007 4 commits
  10. 24 Oct, 2007 1 commit
  11. 14 Oct, 2007 1 commit
  12. 04 Oct, 2007 1 commit
  13. 03 Oct, 2007 2 commits
  14. 02 Oct, 2007 1 commit
  15. 01 Oct, 2007 1 commit
  16. 25 Sep, 2007 1 commit
    • 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
  17. 13 Sep, 2007 2 commits
  18. 12 Sep, 2007 2 commits
  19. 29 Aug, 2007 1 commit
  20. 20 Aug, 2007 4 commits
  21. 16 Aug, 2007 1 commit
  22. 15 Aug, 2007 1 commit
  23. 14 Aug, 2007 3 commits
  24. 13 Aug, 2007 3 commits
  25. 08 Aug, 2007 2 commits
  26. 07 Aug, 2007 1 commit