It turns out that this bug is still reproducible, it just requires index_condition_pushdown=ON.
Full test case:
--source include/have_innodb.inc
CREATE TABLE t1 (
a int NOT NULL,
b int,
c varchar(1),
d varchar(1),
PRIMARY KEY (a),
KEY c (c,b)
) ENGINE=InnoDB;
INSERT INTO t1 VALUES (10,8,'g','g');
SET SESSION optimizer_switch='index_condition_pushdown=ON';
SELECT a FROM t1 WHERE c IS NULL AND d IS NOT NULL GROUP BY 1;
It turns out that this bug is still reproducible, it just requires index_condition _pushdown= ON.
Full test case:
--source include/ have_innodb. inc switch= 'index_ condition_ pushdown= ON';
CREATE TABLE t1 (
a int NOT NULL,
b int,
c varchar(1),
d varchar(1),
PRIMARY KEY (a),
KEY c (c,b)
) ENGINE=InnoDB;
INSERT INTO t1 VALUES (10,8,'g','g');
SET SESSION optimizer_
SELECT a FROM t1 WHERE c IS NULL AND d IS NOT NULL GROUP BY 1;
reproducible on 5.3:
revision-id: <email address hidden>
date: 2011-11-07 16:39:02 +0400
build-date: 2011-11-09 09:40:52 +0200
revno: 3273
branch-nick: maria-5.3
reproducible on 5.3-icp:
revision-id: <email address hidden>
date: 2011-11-08 08:04:48 -0800
build-date: 2011-11-09 09:40:29 +0200
revno: 3272
branch-nick: maria-5.3-icp