Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
5.3.12, 5.5.36, 10.0.9
-
None
-
Centos 6.5 64bit base install
Description
Problem occurs on test table, which consists of two indexed comlumns and primary key column. With following query:
SELECT count(*) |
FROM `test` |
WHERE `col2` = '636146' AND `col1` = '7+'; |
result: 0
Same query while running after:
SET optimizer_switch='index_merge=off'; |
result: 73
I attach my test database, which is derived from production database where issue occurs. I was able to reproduce problem on several other systems.
I was unable to reproduce same error on MySQL 5.5.35
Issue might be related to "intersect(col1,col2);" in query EXPLAIN, while any modification of query (eg. adding OR condition to WHERE expression) seems to avoid the issue. Deleting primary key (which is not involved in query), changing table to MyISAM seems to cause correct behavior of system.
Attachments
Issue Links
- relates to
-
MDEV-5177 ha_partition and innodb index intersection produce fewer rows (MySQL Bug#70703)
- Closed