summaryrefslogtreecommitdiff
path: root/sql
diff options
context:
space:
mode:
authorVarun Gupta <varun.gupta@mariadb.com>2021-03-05 15:30:21 +0530
committerVarun Gupta <varun.gupta@mariadb.com>2021-03-05 15:30:21 +0530
commit01cfc380d332c079168fda61e6c409e0917fafb0 (patch)
tree6394699b49d4822268f474f7054f8df3a8551b61 /sql
parent218c6a6bfb3b6886df9104d6febd144e3bf5b9e1 (diff)
downloadmariadb-git-10.6-mdev8306.tar.gz
Checking whether the join cardinality estimates are accurate should only be done when the order by limit optimization is enabled.
Diffstat (limited to 'sql')
-rw-r--r--sql/sql_select.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/sql/sql_select.cc b/sql/sql_select.cc
index c54e3f9af0a..af63ab7176c 100644
--- a/sql/sql_select.cc
+++ b/sql/sql_select.cc
@@ -8486,7 +8486,7 @@ choose_plan(JOIN *join, table_map join_tables)
Json_writer_object wrapper(thd);
- if (join->conds && (join->sort_nest_possible || thd->trace_started()))
+ if (join->conds && join->sort_nest_possible)
{
bool cardinality_accurate;
SAME_FIELD arg= {NULL, FALSE};