1. 23 Mar, 2007 2 commits
  2. 22 Mar, 2007 14 commits
    • tsmith@siva.hindu.god's avatar
      * · c3ba6eec
      tsmith@siva.hindu.god authored
      * NULL MERGE
      *
      
      Merge siva.hindu.god:/home/tsmith/m/inno/mar22/50
      into  siva.hindu.god:/home/tsmith/m/inno/mar22/51
      
      Null merge of innodb-5.0 snapshots.
      c3ba6eec
    • tsmith@siva.hindu.god's avatar
      Apply the following InnoDB snapshots: · baddc4e9
      tsmith@siva.hindu.god authored
      innodb-5.1-ss1318
      innodb-5.1-ss1330
      innodb-5.1-ss1332
      innodb-5.1-ss1340
      
      Fixes:
      - Bug #21409: Incorrect result returned when in READ-COMMITTED with query_cache ON
        At low transaction isolation levels we let each consistent read set
        its own snapshot.
      
      - Bug #23666: strange Innodb_row_lock_time_% values in show status; also millisecs wrong
        On Windows ut_usectime returns secs and usecs relative to the UNIX
        epoch (which is Jan, 1 1970).
      
      - Bug #25494: LATEST DEADLOCK INFORMATION is not always cleared
        lock_deadlock_recursive(): When the search depth or length is exceeded,
        rewind lock_latest_err_file and display the two transactions at the
        point of aborting the search.
      
      - Bug #25927: Foreign key with ON DELETE SET NULL on NOT NULL can crash server
        Prevent ALTER TABLE ... MODIFY ... NOT NULL on columns for which
        there is a foreign key constraint ON ... SET NULL.
      
      - Bug #26835: Repeatable corruption of utf8-enabled tables inside InnoDB
        The bug could be reproduced as follows:
      
        Define a table so that the first column of the clustered index is
        a VARCHAR or a UTF-8 CHAR in a collation where sequences of bytes
        of differing length are considered equivalent.
      
        Insert and delete a record.  Before the delete-marked record is
        purged, insert another record whose first column is of different
        length but equivalent to the first record.  Under certain conditions,
        the insertion can be incorrectly performed as update-in-place.
      
        Likewise, an operation that could be done as update-in-place can
        unnecessarily be performed as delete and insert, but that would not
        cause corruption but merely degraded performance.
      baddc4e9
    • tsmith@siva.hindu.god's avatar
      NULL MERGE this to 5.1 · 8abc9536
      tsmith@siva.hindu.god authored
      Apply the following InnoDB snapshots:
      innodb-5.0-ss1319
      innodb-5.0-ss1331
      innodb-5.0-ss1333
      innodb-5.0-ss1341
      
      Fixes:
      - Bug #21409: Incorrect result returned when in READ-COMMITTED with query_cache ON
        At low transaction isolation levels we let each consistent read set
        its own snapshot.
      - Bug #23666: strange Innodb_row_lock_time_% values in show status; also millisecs wrong
        On Windows ut_usectime returns secs and usecs relative to the UNIX
        epoch (which is Jan, 1 1970).
      
      - Bug #25494: LATEST DEADLOCK INFORMATION is not always cleared
        lock_deadlock_recursive(): When the search depth or length is exceeded,
        rewind lock_latest_err_file and display the two transactions at the
        point of aborting the search.
      
      - Bug #25927: Foreign key with ON DELETE SET NULL on NOT NULL can crash server
        Prevent ALTER TABLE ... MODIFY ... NOT NULL on columns for which
        there is a foreign key constraint ON ... SET NULL.
      
      - Bug #26835: Repeatable corruption of utf8-enabled tables inside InnoDB
        The bug could be reproduced as follows:
      
        Define a table so that the first column of the clustered index is
        a VARCHAR or a UTF-8 CHAR in a collation where sequences of bytes
        of differing length are considered equivalent.
      
        Insert and delete a record.  Before the delete-marked record is
        purged, insert another record whose first column is of different
        length but equivalent to the first record.  Under certain conditions,
        the insertion can be incorrectly performed as update-in-place.
      
        Likewise, an operation that could be done as update-in-place can
        unnecessarily be performed as delete and insert, but that would not
        cause corruption but merely degraded performance.
      8abc9536
    • tsmith@siva.hindu.god's avatar
      Merge siva.hindu.god:/home/tsmith/m/bk/maint/50 · de07f782
      tsmith@siva.hindu.god authored
      into  siva.hindu.god:/home/tsmith/m/bk/maint/51
      de07f782
    • jonas@perch.ndb.mysql.com's avatar
      Merge joreland@bk-internal.mysql.com:/home/bk/mysql-5.0-ndb · d645496e
      jonas@perch.ndb.mysql.com authored
      into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.0-ndb
      d645496e
    • jonas@perch.ndb.mysql.com's avatar
      Merge perch.ndb.mysql.com:/home/jonas/src/50-work · ca05bbf9
      jonas@perch.ndb.mysql.com authored
      into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.0-ndb
      ca05bbf9
    • jonas@perch.ndb.mysql.com's avatar
      ndb - · 702b5dad
      jonas@perch.ndb.mysql.com authored
        fix test prg
      702b5dad
    • tomas@whalegate.ndb.mysql.com's avatar
      Merge whalegate.ndb.mysql.com:/home/tomas/mysql-5.0-ndb · 47834f39
      tomas@whalegate.ndb.mysql.com authored
      into  whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-new-ndb
      47834f39
    • tomas@whalegate.ndb.mysql.com's avatar
      Merge tulin@bk-internal.mysql.com:/home/bk/mysql-5.0-maint · 8b964c2b
      tomas@whalegate.ndb.mysql.com authored
      into  whalegate.ndb.mysql.com:/home/tomas/mysql-5.0-ndb
      8b964c2b
    • tomas@whalegate.ndb.mysql.com's avatar
      Merge tulin@bk-internal.mysql.com:/home/bk/mysql-5.1-maint · 753bc96e
      tomas@whalegate.ndb.mysql.com authored
      into  whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-new-ndb
      753bc96e
    • tomas@whalegate.ndb.mysql.com's avatar
      Merge tulin@bk-internal.mysql.com:/home/bk/mysql-5.1 · 6e7528bd
      tomas@whalegate.ndb.mysql.com authored
      into  whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-new-ndb
      6e7528bd
    • tomas@whalegate.ndb.mysql.com's avatar
      Merge tulin@bk-internal.mysql.com:/home/bk/mysql-5.0 · 6bab2f13
      tomas@whalegate.ndb.mysql.com authored
      into  whalegate.ndb.mysql.com:/home/tomas/mysql-5.0-ndb
      6bab2f13
    • tsmith@quadxeon.mysql.com's avatar
      Merge quadxeon.mysql.com:/benchmarks/ext3/TOSAVE/tsmith/bk/maint/50 · c0d1f9fd
      tsmith@quadxeon.mysql.com authored
      into  quadxeon.mysql.com:/benchmarks/ext3/TOSAVE/tsmith/bk/maint/51
      c0d1f9fd
    • tsmith@quadxeon.mysql.com's avatar
      Merge tsmith@bk-internal.mysql.com:/home/bk/mysql-5.1 · 54e7bc8d
      tsmith@quadxeon.mysql.com authored
      into  quadxeon.mysql.com:/benchmarks/ext3/TOSAVE/tsmith/bk/maint/51
      54e7bc8d
  3. 21 Mar, 2007 24 commits