• Sergei Petrunia's avatar
    MDEV-34720: Poor plan choice for large JOIN with ORDER BY and small LIMIT · c8d04093
    Sergei Petrunia authored
    (Variant 2b: call greedy_search() twice, correct handling for limited
     search_depth)
    
    Modify the join optimizer to specifically try to produce join orders that
    can short-cut their execution for ORDER BY..LIMIT clause.
    
    The optimization is controlled by @@optimizer_join_limit_pref_ratio.
    Default value 0 means don't construct short-cutting join orders.
    Other value means construct short-cutting join order, and prefer it only
    if it promises speedup of more than #value times.
    
    In Optimizer Trace, look for these names:
    * join_limit_shortcut_is_applicable
    * join_limit_shortcut_plan_search
    * join_limit_shortcut_choice
    c8d04093
sysvars_server_embedded.result 134 KB