summaryrefslogtreecommitdiff
path: root/sql/opt_range.cc
diff options
context:
space:
mode:
authorSergey Petrunya <psergey@askmonty.org>2014-04-21 15:37:55 +0400
committerSergey Petrunya <psergey@askmonty.org>2014-04-21 15:37:55 +0400
commitdeb26989e91921965d5b588f85acecf3bbc771db (patch)
treed12cf082c8d3ceb8f312bf42edf69af7b5ba5444 /sql/opt_range.cc
parent872a01b6b1a9cb435a0c7c57da73fbd0f806fd80 (diff)
downloadmariadb-git-deb26989e91921965d5b588f85acecf3bbc771db.tar.gz
MDEV-5980: EITS: if condition is used for REF access, its selectivity is still in filtered%
MDEV-5985: EITS: selectivity estimates look illogical for join and non-key equalities MDEV-6003: EITS: ref access, keypart2=const vs keypart2=expr - inconsistent filtered% value - Made a number of fixes in table_cond_selectivity() so that it returns correct selectivity estimates. - Added comments in related code.
Diffstat (limited to 'sql/opt_range.cc')
-rw-r--r--sql/opt_range.cc4
1 files changed, 4 insertions, 0 deletions
diff --git a/sql/opt_range.cc b/sql/opt_range.cc
index d4f171321e0..bfcb7e4a54f 100644
--- a/sql/opt_range.cc
+++ b/sql/opt_range.cc
@@ -3406,6 +3406,10 @@ double records_in_column_ranges(PARAM *param, uint idx,
selectivity (this is used for conditions like "column LIKE '%val%'"
where approaches #1 and #2 do not provide selectivity data).
+ SEE ALSO
+ table_cond_selectivity()
+ matching_candidates_in_table()
+
NOTE
Currently the selectivities of range conditions over different columns are
considered independent.