-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 10.1
-
Fix Version/s: 10.2.6
-
Component/s: Storage Engine - Spider
-
Labels:None
-
Environment:Ubuntu
-
Sprint:2017-02, 10.1.22
set global optimizer_switch="engine_condition_pushdown=on"
Ouch! It is now pulling back the entire table 200 rows at a time.
Query: SELECT DISTINCT x FROM table
PRIMARY KEY (x,y,z)
Backend queries: SELECT x FROM table x > 12345 ORDER BY x,y,z LIMIT 200.
(And it is taking much longer than when ecp=OFF)
Question 1: Why fetch the table rather than executing the query?
Question 2: When you have a multi-part PK, that code is likely to be "wrong". Note that it always compared only x, not y and z. And it always said 200.
- causes
-
MDEV-13282 post-fix for MDEV-8954
-
- Open
-