- 04 May, 2006 17 commits
-
-
monty@mysql.com authored
mysql-test-run now fails in case of warnings
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.0
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.0
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.0
-
monty@mysql.com authored
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.0
-
jani@ua141d10.elisa.omakaista.fi authored
into ua141d10.elisa.omakaista.fi:/home/my/bk/mysql-5.0
-
jani@ua141d10.elisa.omakaista.fi authored
is only to make sure that this will not be fixed, as it is intended behaviour. Documentation will be improved accordingly.
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.0
-
monty@mysql.com authored
This caused sp-vars.test to fail
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
svoj@april.(none) authored
-
holyfoot@mysql.com authored
into mysql.com:/home/hf/work/mysql-5.0.mrg
-
holyfoot@mysql.com authored
into mysql.com:/home/hf/work/mysql-5.0.mrg
-
holyfoot@deer.(none) authored
-
igor@rurik.mysql.com authored
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
- 03 May, 2006 22 commits
-
-
svojtovich@production.mysql.com authored
into production.mysql.com:/usersnfs/svojtovich/mysql-5.0
-
holyfoot@mysql.com authored
into mysql.com:/home/hf/work/mysql-5.0.mrg
-
pekka@mysql.com authored
into mysql.com:/space/pekka/ndb/version/my50
-
aivanov@mysql.com authored
into mysql.com:/home/alexi/innodb/mysql-5.0-ss521
-
aivanov@mysql.com authored
Fixed BUG#19366: "consistent_snapshot.test fails".
-
holyfoot@mysql.com authored
into mysql.com:/home/hf/work/mysql-4.1.mrg
-
aivanov@mysql.com authored
into mysql.com:/home/alexi/innodb/mysql-4.1-ss26
-
aivanov@mysql.com authored
into mysql.com:/home/alexi/innodb/mysql-5.0-ss521-work Null-merge.
-
aivanov@mysql.com authored
Fixed BUG#19366: "consistent_snapshot.test fails".
-
holyfoot@mysql.com authored
into mysql.com:/home/hf/work/mysql-4.1.mrg
-
holyfoot@deer.(none) authored
-
holyfoot@deer.(none) authored
-
holyfoot@mysql.com authored
into mysql.com:/home/hf/work/mysql-5.0.mrg
-
holyfoot@mysql.com authored
-
holyfoot@mysql.com authored
-
svoj@april.(none) authored
into april.(none):/home/svoj/devel/mysql/BUG17810/mysql-5.0
-
svoj@april.(none) authored
into april.(none):/home/svoj/devel/mysql/BUG17810/mysql-5.0
-
holyfoot@mysql.com authored
-
holyfoot@mysql.com authored
into mysql.com:/home/hf/work/mysql-4.1.mrg
-
holyfoot@mysql.com authored
into mysql.com:/home/hf/work/mysql-4.1.mrg
-
holyfoot@mysql.com authored
into mysql.com:/home/hf/work/mysql-4.1.mrg
-
igor@rurik.mysql.com authored
This performance degradation was due to the fact that some cost evaluation code added into 4.1 in the function find_best was not merged into the code of the function best_access_path added together with other code for greedy optimizer. Added a parameter to the function print_plan. The parameter contains accumulated cost for a given partial join. The patch does not include a special test case since this performance degradation is hard to reproduse with a simple example. TODO: make the function find_best use the function best_access_path in order to remove duplication of code which might result in incomplete merges in the future.
-
- 02 May, 2006 1 commit
-
-
pekka@mysql.com authored
-