[MDEV-3688] LP:887026 - Wrong result with ICP, outer join, subquery in maria-5.3-icp Created: 2011-11-07 Updated: 2015-02-02 Resolved: 2012-10-04 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Philip Stoev (Inactive) | Assignee: | Sergei Petrunia |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | Launchpad | ||
| Attachments: |
|
| Description |
|
The following query: SELECT * returns no rows when executed with maria-5.3-icp and index_condition_pushdown=ON and {c,NULL}in all other cases. The issue is also reproducible without empty/constant tables. The issue is also reproducible with realistic ON conditions. explain: id select_type table type possible_keys key key_len ref rows Extra minimal switch: index_condition_pushdown=ON; bzr version-info test case: CREATE TABLE t1 ( c varchar(1)) ENGINE=InnoDB; CREATE TABLE t2 ( b int) ENGINE=InnoDB; CREATE TABLE t3 ( c varchar(1)) ENGINE=InnoDB; CREATE TABLE t4 ( b int, c varchar(1), KEY (b)) ENGINE=InnoDB; SET SESSION optimizer_switch='index_condition_pushdown=ON'; |
| Comments |
| Comment by Sergei Petrunia [ 2011-11-07 ] |
|
Re: Wrong result with ICP, outer join, subquery in maria-5.3-icp CREATE TABLE t1 (c varchar(1)); CREATE TABLE t2 (c varchar(1), b int); CREATE TABLE t3 (c varchar(1)); CREATE TABLE t4 ( b int, c varchar(1), KEY (b)); SET SESSION optimizer_switch='index_condition_pushdown=ON'; |
| Comment by Rasmus Johansson (Inactive) [ 2011-12-13 ] |
|
Launchpad bug id: 887026 |