diff options
author | Varun Gupta <varun.gupta@mariadb.com> | 2020-08-18 17:31:10 +0530 |
---|---|---|
committer | Varun Gupta <varun.gupta@mariadb.com> | 2020-08-19 14:45:19 +0530 |
commit | d08b9d3c1c5be5dc183b1384730973be0e70c44d (patch) | |
tree | 4463a9041ea33e822be6b4949f2afb21f8e5f53d /sql/sql_union.cc | |
parent | 8ddc2182fdfd8f8b8dcffccb4605cd9deac35c7a (diff) | |
download | mariadb-git-10.1-varun.tar.gz |
MDEV-23160: SIGSEGV in Explain_node::print_explain_for_children on UNION SELECT or on EXPLAIN EXTENDED10.1-varun
The issue here was that the ORDER BY clause had a subquery and the
ORDER BY clause was defined for a UNION inside an IN subquery.
For IN/ALL/ANY subquery the ORDER BY clause makes no sense and should be removed.
But the removal of the ORDER BY clause happened before name resolution. So an invalid query
could also be parsed and would not return an error.
The reason for the crash is that for EXPLAIN of UNION, the fake_select_lex adds the
removed subquery as its child. The subquery being removed does not create a node for itself
for EXPLAIN. But when the EXPLAIN is printed for the fake_select_lex it tries to print the nodes
of its children.
The fix would be to mark the subquery to be eliminated so that it is not added as a child
to the fake_select_lex node. Then after name resolution is done and the query is valid
then remove the subquery so that it does not get executed.
Diffstat (limited to 'sql/sql_union.cc')
-rw-r--r-- | sql/sql_union.cc | 48 |
1 files changed, 29 insertions, 19 deletions
diff --git a/sql/sql_union.cc b/sql/sql_union.cc index 0e623777ef0..3f03baf73ec 100644 --- a/sql/sql_union.cc +++ b/sql/sql_union.cc @@ -331,6 +331,35 @@ st_select_lex_unit::init_prepare_fake_select_lex(THD *thd_arg, (*order->item)->walk(&Item::set_fake_select_as_master_processor, 0, (uchar*) fake_select_lex); } + + /* + If we are reading UNION output and the UNION is in the + IN/ANY/ALL subquery, then ORDER BY is redundant and hence should + be removed. + Example: + select ... col IN (select col2 FROM t1 union select col3 from t2 ORDER BY 1) + + (as for ORDER BY ... LIMIT, it currently not supported inside + IN/ALL/ANY subqueries) + ORDER BY LIMIT is allowed in EXISTS subqueries, so we don't remove + the ORDER BY clause from EXISTS subqueries + (For non-UNION this removal of ORDER BY clause is done in + check_and_do_in_subquery_rewrites()) + @see remove_redundant_subquery_clauses + */ + if (is_union_op_inside_in_predicate()) + { + for (ORDER *ord= global_parameters()->order_list.first; ord; ord= ord->next) + { + /* + The subqueries inside the ORDER BY clause are marked as eliminated. + This is done to avoid adding the subqueries as children of the + fake_select_lex in the EXPLAIN structures. + */ + (*ord->item)->walk(&Item::mark_as_eliminated_processor, FALSE, NULL); + } + } + } @@ -388,25 +417,6 @@ bool st_select_lex_unit::prepare(THD *thd_arg, select_result *sel_result, found_rows_for_union= first_sl->options & OPTION_FOUND_ROWS; is_union_select= is_union() || fake_select_lex; - /* - If we are reading UNION output and the UNION is in the - IN/ANY/ALL/EXISTS subquery, then ORDER BY is redundant and hence should - be removed. - Example: - select ... col IN (select col2 FROM t1 union select col3 from t2 ORDER BY 1) - - (as for ORDER BY ... LIMIT, it currently not supported inside - IN/ALL/ANY subqueries) - (For non-UNION this removal of ORDER BY clause is done in - check_and_do_in_subquery_rewrites()) - */ - if (is_union() && item && - (item->is_in_predicate() || item->is_exists_predicate())) - { - global_parameters()->order_list.first= NULL; - global_parameters()->order_list.elements= 0; - } - /* Global option */ if (is_union_select) |