gkodinov/kgeorge@macbook.gmz
fe03f6bbe0
Bug #27531 : 5.1 part of the fix
...
- Renamed "Using join cache" to "Using join buffer".
- "Using join buffer" is now printed on the last
table that "reads" from the join buffer cache.
2007-05-29 15:58:18 +03:00
gkodinov/kgeorge@magare.gmz
306371a850
bug #27531 : 5.1 part of the fix:
...
- added join cache indication in EXPLAIN (Extra column).
- prefer filesort over full scan over
index for ORDER BY (because it's faster).
- when switching from REF to RANGE because
RANGE uses longer key turn off sort on
the head table only as the resulting
RANGE access is a candidate for join cache
and we don't want to disable it by sorting
on the first table only.
2007-05-04 18:06:06 +03:00
sergefp@mysql.com
cd094b71af
BUG#14940: Update test results
2006-09-29 20:42:37 +04:00
timour@mysql.com
68c2309a66
Fix for BUG#7266.
2004-12-16 16:44:40 +02:00
bell@sanja.is.com.ua
c5a84657a8
standard values for table type in SHOW TABLES (BUG#4603)
2004-07-19 12:07:33 +03:00
timour@mysql.com
432b842e23
Better names for two system variables:
...
- heuristic => optimizer_prune_level
- plan_search_depth => optimizer_search_depth
2004-05-20 17:47:43 +03:00
pem@mysql.comhem.se
9ec93a8948
Post-merge post-merge post fix. ;-)
2004-05-14 17:47:11 +02:00
timour@mysql.com
a840d8daad
Complete implementation of WL#1469 "Greedy algorithm to search for an optimal execution plan",
...
consisting of pos-review fixes and improvements.
2004-05-10 15:48:50 +03:00
timour@mysql.com
9f1fd5bd90
Implementation of WL#1469 (Greedy algorithm to search for an optimal execution plan).
2004-04-16 13:21:08 +03:00
