Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
N/A
Description
CURRENT_TEST: tokudb_mariadb.mdev6657
|
--- /usr/local/mariadb-10.1.1-linux-x86_64/mysql-test/plugin/tokudb/tokudb_mariadb/r/mdev6657.result 2014-10-06 11:54:56.000000000 +0300
|
+++ /usr/local/mariadb-10.1.1-linux-x86_64/mysql-test/plugin/tokudb/tokudb_mariadb/r/mdev6657.reject 2014-10-06 16:30:44.327828045 +0300
|
@@ -34,7 +34,7 @@
|
where col1 <= 1410799999
|
order by col1 desc,col2 desc,col3 desc limit 1;
|
id select_type table type possible_keys key key_len ref rows Extra
|
-1 SIMPLE t3 range PRIMARY,key1 PRIMARY 4 NULL 2001 Using where; Using index
|
+1 SIMPLE t3 range PRIMARY,key1 key1 4 NULL 2001 Using where; Using index
|
# The same query but the constant is bigger.
|
# The query should use range(PRIMARY), not full index scan:
|
explain
|
@@ -43,5 +43,5 @@
|
where col1 <= 1412199999
|
order by col1 desc, col2 desc, col3 desc limit 1;
|
id select_type table type possible_keys key key_len ref rows Extra
|
-1 SIMPLE t3 range PRIMARY,key1 PRIMARY 4 NULL 15001 Using where; Using index
|
+1 SIMPLE t3 range PRIMARY,key1 key1 4 NULL 15001 Using where; Using index
|
drop table t1,t2,t3;
|
I got the same failure while running the single test on my machine.
Attachments
Issue Links
- relates to
-
MDEV-6657 Poor plan choice for ORDER BY key DESC optimization and possible range access
- Closed