- no check was made that ndb thd object was allocated

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

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

-flag was set on field intable share instead of table

into  mysql.com:/users/lthalmann/bk/mysql-5.1-new-bug17339

into  mysql.com:/users/lthalmann/bkroot/mysql-5.1-new

into  mysql.com:/users/lthalmann/bk/mysql-5.1-new-bug17339

into  zim.tangent.org:/home/brian/mysql/cleanup-5.1

BUG#17339: Most rpl tests need to execute sync_slave_with_master to ensure that cleanup is done on slave
For this particular bug report it was rpl_loadfile.test that did not make proper cleanup, but the patch
includes fixes for other tests aswell.

into  mysql.com:/users/lthalmann/bkroot/mysql-5.1-new

into  snake-hub.snake.net:/src/extern/MySQL/bk/mysql-5.1

  Fix out-of-order system variable.

    "Use remote": Let the other changes (test the debug binary) precede.

into  mysql.com:/users/lthalmann/bkroot/mysql-5.1-new

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

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

into  selena.:H:/MYSQL/src/#00001-mysql-5.1

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

wrong arrGuard, see MAX_REPLICAS+1 0n row 6457
+ changed all 4 constants to MAX_REPLICAS
+ moved some arrGuards out of loops for optim reasons

into  selena.:H:/MYSQL/src/#00001-mysql-5.1

into  mysql.com:/users/lthalmann/bkroot/mysql-5.1-new

into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.0

Disabling a test, I will look at it tomorrow. Something is wrong with the merge from 5.0. Its probably a flush that is missing somewhere but I am too tired to figure it out at the moment.

into  zim.tangent.org:/home/brian/mysql/cleanup-5.1

into  mysql.com:/home/alik/Documents/AllProgs/MySQL/devel/5.1-tree

into  zim.tangent.org:/home/brian/mysql/cleanup-5.1

Discoved while debugging in 5.1 that there was a bug where a certain crash could lead to two problems. 1) An additional share in memory that was allocated but did not have the correct use_count (so it would never be fulled deleted). Also discovered that a thread that called repair would write new rows, but would not see them. All other threads were ok, and the data was fine, but the thread doing the repair was unable to see the new rows.

into  mysql.com:/home/alik/Documents/AllProgs/MySQL/devel/5.1-tree

into  zim.tangent.org:/home/brian/mysql/cleanup-5.1

Cleanup's from Kostja's review. Plus I added a bit more documentation to the --lock-tables option. If selected it disables threads (since you can't quite do it with threads).

'--log-bin-trust-function-creators' affects not only replication of the
stored functions, but also replication of the triggers.

add optional reporting of of a "name" tied to a nodeid in the cluster log
reporting added for mysql server and ndb_restore

into  zim.tangent.org:/home/brian/mysql/cleanup-5.1