• Sergei Petrunia's avatar
    MDEV-28929: Plan selection takes forever with MDEV-28852 ... · 8c2faad5
    Sergei Petrunia authored
    Part #2: Extend heuristic pruning to use multiple tables as the
    "Model tables".
    
    Before the patch, heuristic pruning uses only one "Model table":
    The table which had the best cost AND record became the "Model table".
    After that, if a table's cost and record were both worse than
    those of the Model Table, the table would be pruned away.
    
    This didn't work well when the first table (the optimizer sorts them
    by record_count) had low record_count but relatively high cost: nothing
    could be pruned afterwards.
    
    The patch adds the two additional "Model tables": one with the least
    cost and the other with the least record_count.
    (In both cases, a table can be pruned away if BOTH its cost and
    record_count are worse than those of a Model table)
    
    The new pruning is active when the number of tables to consider for
    the prefix is higher than @@optimizer_extra_pruning_depth.
    
    One can see the new pruning in the Optimizer Trace as
    - "pruned_by_heuristic":"min_record_count", or
    - "pruned_by_heuristic":"min_read_time".
    Old heuristic pruning shows as "pruned_by_heuristic":1.
    8c2faad5
sql_select.h 84.1 KB