maria-developers team mailing list archive

[Kristian Nielsen <knielsen@xxxxxxxxxxxxxxx>]

Hi Paul,

I'm merging MySQL 5.1.46 into MariaDB. But I hit a test failure in PBXT, see
below.

It is wrong result from a SELECT. Interestingly, the same SELECT in the main
test suite seems to work correctly.

The code is in

    lp:~maria-captains/maria/5.1-release

Can you maybe take a look, in case it is a PBXT issue? Probably also one of
our optimiser people should take a look to see if it is a server problem. It's
a bit strange that it seems to be pbxt specific, I'm wondering if there was a
subtle change of the storage engine API introduced or something?

Test failure link and output below.

 - Kristian.


    http://buildbot.askmonty.org/buildbot/reports/cross_reference#branch=5.1-release&revision=2855&platform=&dt=&bbnum=&typ=&info=&fail_name=pbxt.join&fail_variant=&fail_info_short=&fail_info_full=&limit=100

Test case pbxt.join

pbxt.join                                w4 [ fail ]
        Test ended at 2010-04-28 22:47:39

CURRENT_TEST: pbxt.join
--- /space3/buildbot/makedist/build/install/mysql-test/suite/pbxt/r/join.result	2010-04-28 22:12:50.000000000 +0200
+++ /space3/buildbot/makedist/build/install/mysql-test/suite/pbxt/r/join.reject	2010-04-28 22:47:39.000000000 +0200
@@ -59,14 +59,13 @@
 107	1
 select t1.id,t2.id from t2 left join t1 on t1.id>=74 and t1.id<=0 where t2.id=75 and t1.id is null;
 id	id
-NULL	75
 explain select t1.id,t2.id from t2 left join t1 on t1.id>=74 and t1.id<=0 where t2.id=75 and t1.id is null;
 id	select_type	table	type	possible_keys	key	key_len	ref	rows	Extra
-1	SIMPLE	t1	const	PRIMARY	NULL	NULL	NULL	1	Impossible ON condition
-1	SIMPLE	t2	ALL	NULL	NULL	NULL	NULL	3	Using where
+1	SIMPLE	NULL	NULL	NULL	NULL	NULL	NULL	NULL	Impossible WHERE noticed after reading const tables
 explain select t1.id, t2.id from t1, t2 where t2.id = t1.id and t1.id <0 and t1.id > 0;
 id	select_type	table	type	possible_keys	key	key_len	ref	rows	Extra
-1	SIMPLE	NULL	NULL	NULL	NULL	NULL	NULL	NULL	Impossible WHERE noticed after reading const tables
+1	SIMPLE	t2	ALL	NULL	NULL	NULL	NULL	3	Using where
+1	SIMPLE	t1	eq_ref	PRIMARY	PRIMARY	4	test.t2.id	1	Using index
 drop table t1,t2;
 CREATE TABLE t1 (
 id int(11) NOT NULL auto_increment,

mysqltest: Result length mismatch