Q13 from DBT3 uses table scan instead of covering index scan
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MariaDB |
Fix Committed
|
Critical
|
Igor Babaev |
Bug Description
This is MariaDB-5.5.23 (GA, as released). DBT3 data at SF30 loaded into InnoDB tables. Default statistics (fluctuating). Running EXPLAIN for Q13 10 times, restarting the server in between. Yields 10 times the same (bad) plan. Earlier tests resulted in exactly this plan 100 times in 100 tries.
How to reproduce:
login to facebook-maria1
cd ~/benchmark/
~/benchmark/
(this is one single line)
after that there will be a new results directory "innodb_
Attached is the tarred results directory from the run I've done just now.
Changed in maria: | |
milestone: | none → 5.5 |
assignee: | nobody → Igor Babaev (igorb-seattle) |
importance: | Undecided → Critical |
status: | Confirmed → In Progress |
commandline saved in bug999251.sh. To reproduce:
cd ~/benchmark/ dbt3/mariadb- tools/dbt3_ benchmark
./bug999251.sh
this runs in about 1 minute