MariaDB

index_merge/interesection is picked when it seems to be the best plan

Bug #1007806 reported by Sergey Petrunia
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MariaDB
New
Low
Sergey Petrunia

Bug Description

Look at the testcase for https://bugs.launchpad.net/maria/+bug/1006164. The DELETE statement (but not its SELECT analog for some reason) uses index_merge/intersect strategy. This choice looks a bit odd, because each of the merged scans selects only a few records.

I'm not stating the choice is wrong, but this example is something we could look at when/if we're going to tune index_merge cost model.

Sergey Petrunia (sergefp)
Changed in maria:
assignee: nobody → Sergey Petrunia (sergefp)
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.