• unknown's avatar
    Fix for MDEV-4144 · 599a1384
    unknown authored
      
    Analysis:
    The reason for the inefficent plan was that Item_subselect::is_expensive()
    didn't detect the special case when a subquery was optimized, but had no
    join plan because it either has no table, or its tables have been optimized
    away, or the optimizer detected that the result set is empty.
      
    Solution:
    Identify the special cases above in the Item_subselect::is_expensive(),
    and consider such degenerate subqueries inexpensive.
    599a1384
func_group.result 64.9 KB