mirror of
https://github.com/MariaDB/server.git
synced 2025-01-29 18:20:07 +01:00
272e5e6212
even in the cases when there existed range/index-merge scans that were cheaper than the full table scan. This was a defect/bug of the implementation of mwl #128. Now hash join can work not only with full table scan of the joined table, but also with full index scan, range and index-merge scans. Accordingly, in the cases when hash join is used the column 'type' in the EXPLAINs can contain now 'hash_ALL', 'hash_index', 'hash_range' and 'hash_index_merge'. If hash join is coupled with a range/index_merge scan then the columns 'key' and 'key_len' contain info not only on the used hash index, but also on the indexes used for the scan. |
||
|---|---|---|
| .. | ||
| binlog | ||
| bugs | ||
| engines | ||
| federated | ||
| funcs_1 | ||
| funcs_2 | ||
| ibmdb2i | ||
| im | ||
| innodb | ||
| innodb_plugin | ||
| jp | ||
| large_tests | ||
| manual | ||
| maria | ||
| ndb | ||
| ndb_team | ||
| optimizer_unfixed_bugs | ||
| oqgraph | ||
| parts | ||
| pbxt | ||
| percona | ||
| rpl | ||
| rpl_ndb | ||
| sphinx | ||
| stress | ||
| sys_vars | ||
| vcol | ||