• Monty's avatar
    Fix cost calculation in test_if_cheaper_ordering() to be cost based · 013ba37a
    Monty authored
    The original code was mostly rule based and preferred clustered or
    covering indexed independent of cost.
    
    There where a few test changes:
    - Some test changed from using filesort to index or table scan. This
      happened when most of the rows had to be sorted and the ORDER BY could
      use covering or a clustered index (innodb_mysql, create_spatial_index).
    - Some test changed range to filesort. This where mainly because the range
      was scanning most of the rows or using index scan + row lookup and
      filesort with table scan is cheaper. (order_by).
    - Change in join_cache was because sorting 2 rows is faster than retrieving
      10 rows.
    - In selectivity_innodb.test one test changed to use a cheaper index.
    013ba37a
opt_trace.result 458 KB