into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new-ndb-merge

default changed not to run idempotent, but test requires it because of how ndb logs updates as write

  fix failing autotest-test

  Using more than 16g can cause record-pool ptr.i values to overflow
  Fix by splitting memory into 2 zones, lo(16g)/hi(rest)
  When record pools only use zone_lo, and datamemory, buffers etc...can use any

into  pilot.mysql.com:/data/msvensson/mysql/mysql-5.1-ndb

into  pilot.mysql.com:/data/msvensson/mysql/mysql-5.1-ndb

into  whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-new-ndb-merge

into  mysql.com:/home/marty/MySQL/mysql-5.1-new-ndb

into  pilot.mysql.com:/data/msvensson/mysql/mysql-5.1-ndb

  During TC-take-over (NF) the new-TC builds up a new transaction state
  And commits operation according to this state.
  However, in the new state that is build, the operations does not have to be in same order, as "real" state
  In the multi-update-case, this means that operations can be commit in "incorrect" order

  i.e update A, delete A, insert A is normally commited in same order as prepared
      but can be committed in any order

  This patch changes TUP handling of these out-order commits, and previous implementation
    could confuse the TUX triggers

  testcases

cause sporadic, but benign, errors.

into  poseidon.ndb.mysql.com:/home/tomas/cge-5.1

- in autocommit do not allocate statistics share, but instead use one directly on the handler

into  sama.ndb.mysql.com:/export/space/pekka/ndb/version/my51-ndb

into  dl145h.mysql.com:/data0/mkindahl/mysql-5.1-rpl-merge

into  dl145h.mysql.com:/data0/mkindahl/mysql-5.1-rpl-merge

into  sama.ndb.mysql.com:/export/space/pekka/ndb/version/my51-ndb

  make sure to alloc logspace and set bits
  if doing delete after previous update wo/ touching DD part

into  perch.ndb.mysql.com:/home/jonas/src/51-ndb

  remove incorrect ndbrequire

           exists t1,t2,t3'
Bug #34245 Test ndb_binlog_multi fails for 'CREATE TABLE'
Bug #34246 Test rpl_ndb_transaction fails with 'Failed to create
           'mysql/ndb_apply_status'

Tests cases didn't wait for cluster to come up due to a typo
in have_multi_ndb.inc.

into  mysql.com:/usr/clones/mysql-5.1-new-ndb2