- 13 Feb, 2006 40 commits
-
-
lars@mysql.com authored
into mysql.com:/users/lthalmann/bk/mysql-5.1-new-bug17339
-
lars@mysql.com authored
into mysql.com:/users/lthalmann/bkroot/mysql-5.1-new
-
lars@mysql.com authored
into mysql.com:/users/lthalmann/bk/mysql-5.1-new-bug17339
-
brian@zim.tangent.org authored
into zim.tangent.org:/home/brian/mysql/cleanup-5.1
-
brian@zim.tangent.org authored
-
joerg@mysql.com authored
-
lars@mysql.com authored
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.
-
lars@mysql.com authored
into mysql.com:/users/lthalmann/bkroot/mysql-5.1-new
-
paul@snake-hub.snake.net authored
into snake-hub.snake.net:/src/extern/MySQL/bk/mysql-5.1
-
paul@snake-hub.snake.net authored
Fix out-of-order system variable.
-
joerg@mysql.com authored
"Use remote": Let the other changes (test the debug binary) precede.
-
joerg@mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
-
lars@mysql.com authored
into mysql.com:/users/lthalmann/bkroot/mysql-5.1-new
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new
-
SergeyV@selena. authored
into selena.:H:/MYSQL/src/#00001-mysql-5.1
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new
-
tomas@poseidon.ndb.mysql.com authored
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
-
SergeyV@selena. authored
into selena.:H:/MYSQL/src/#00001-mysql-5.1
-
lars@mysql.com authored
into mysql.com:/users/lthalmann/bkroot/mysql-5.1-new
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0
-
brian@zim.tangent.org authored
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.
-
tomas@poseidon.ndb.mysql.com authored
-
brian@zim.tangent.org authored
into zim.tangent.org:/home/brian/mysql/cleanup-5.1
-
brian@zim.tangent.org authored
-
anozdrin@mysql.com authored
into mysql.com:/home/alik/Documents/AllProgs/MySQL/devel/5.1-tree
-
brian@zim.tangent.org authored
into zim.tangent.org:/home/brian/mysql/cleanup-5.1
-
brian@zim.tangent.org authored
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.
-
anozdrin@mysql.com authored
into mysql.com:/home/alik/Documents/AllProgs/MySQL/devel/5.1-tree
-
brian@zim.tangent.org authored
into zim.tangent.org:/home/brian/mysql/cleanup-5.1
-
brian@zim.tangent.org authored
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).
-
anozdrin@mysql.com authored
'--log-bin-trust-function-creators' affects not only replication of the stored functions, but also replication of the triggers.
-
tomas@poseidon.ndb.mysql.com authored
add optional reporting of of a "name" tied to a nodeid in the cluster log reporting added for mysql server and ndb_restore
-
brian@zim.tangent.org authored
into zim.tangent.org:/home/brian/mysql/cleanup-5.1
-
lars@mysql.com authored
into mysql.com:/users/lthalmann/bkroot/mysql-5.1-new
-
brian@zim.tangent.org authored
Adding thread support for mysqlimport. You can now specify a number of threads to use and it will thread the loading of the database. Anyone who has had to go through the pain of loading the database will immediatly get the reason for this.
-
bar@mysql.com authored
into mysql.com:/usr/home/bar/mysql-5.1-new.fscs
-
bar@mysql.com authored
new file Many files: WL#757 RENAME DATABASE
-
brian@zim.tangent.org authored
-