Date: 2012-05-29 10:46:01 +0200
From: Inho Kim <<georgios.kim>>
To: SQL devs <>
Version: -- development
CC: @njnes

Last updated: 2012-06-19 11:20:37 +0200

Comment 17295

Date: 2012-05-29 10:46:01 +0200
From: Inho Kim <<georgios.kim>>

User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.52 Safari/536.5
Build Identifier: MonetDB v11.9.5

mserver5 crashed if join condition has two column and incorrect order..

select * from test1 a, test2 b where a.id = b.id and a.seq = b.seq; => OK

select * from test1 a, test2 b where a.id = b.id and b.seq = a.seq; => crash

Reproducible: Always

Steps to Reproduce:

1.create table test1 ( id int, seq int, name varchar(20));
2.create table test2 ( id int, seq int, name varchar(20));
3.select * from test1 a, test2 b where a.id = b.id and b.seq = a.seq;

Actual Results:

mserver5 crashed..

Comment 17299

Date: 2012-05-29 17:43:56 +0200
From: @njnes

I'm unable to reproduce this crash with Apr2012/Jul2012 or tip

Comment 17301

Date: 2012-05-30 04:24:11 +0200
From: Inho Kim <<georgios.kim>>

sorry for wrong example..

Please check out following example..

create table test1 ( id int, seq int, name varchar(20), primary key (id, seq));
create table test2 ( id int not null, seq int not null, name varchar(20));

select * from test1 a, test2 b where a.id = b.id and b.seq = a.seq;

Comment 17302

Date: 2012-05-30 09:25:22 +0200
From: @njnes

Changeset 0f98dc926be5 made by Niels Nes niels@cwi.nl in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0f98dc926be5

Changeset description:

fixed crashing bug #3089
handle hash joins on partials keys

Comment 17303

Date: 2012-05-30 09:28:29 +0200
From: @njnes

indeed this example crashes (asserts). Fixed, in case the hash join fails fall back to normal join.