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.

1 files changed, 7 insertions, 0 deletions

diff --git a/sql/sql_select.cc b/sql/sql_select.cc
index 7a1a7baaa1c..912f28d7168 100644
--- a/sql/sql_select.cc
+++ b/sql/sql_select.cc
@@ -590,6 +590,13 @@ void remove_redundant_subquery_clauses(st_select_lex *subq_select_lex)
     DBUG_PRINT("info", ("DISTINCT removed"));
   }
 
+  if (subq_select_lex->master_unit()->is_union_op_inside_in_predicate() &&
+      subq_select_lex->master_unit()->fake_select_lex == subq_select_lex &&
+      subq_select_lex->order_list.elements)
+  {
+    subq_select_lex->join->order= NULL;
+  }
+
   /*
     Remove GROUP BY if there are no aggregate functions and no HAVING
     clause