[MDEV-4270] crash in fix_semijoin_strategies_for_picked_join_order Created: 2013-03-13  Updated: 2013-05-04  Resolved: 2013-05-04

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.1, 5.5.30, 5.1.67, 5.2.14, 5.3.12
Fix Version/s: 10.0.3, 5.5.31, 5.1.73, 5.2.15, 5.3.13

Type: Bug Priority: Major
Reporter: sbester1 Assignee: Sergei Petrunia
Resolution: Fixed Votes: 0
Labels: None
Environment:

winx64, linux x64


Issue Links:
Relates
relates to MDEV-621 LP:693329 - Assertion `!is_interleave... Closed

 Description   

Initial valgrind error from maria revno 3503: (release build)

Use of uninitialised value of size 8
at: fix_semijoin_strategies_for_picked_join_order (opt_subselect.cc:3191)
by: get_best_combination (sql_select.cc:7672)
by: make_join_statistics (sql_select.cc:3864)
by: JOIN::optimize_inner (sql_select.cc:1264)
by: JOIN::optimize (sql_select.cc:986)
by: mysql_select (sql_select.cc:3178)
by: handle_select (sql_select.cc:363)
by: execute_sqlcom_select (sql_parse.cc:5004)
by: mysql_execute_command (sql_parse.cc:2472)
by: mysql_parse (sql_parse.cc:6124)
by: dispatch_command (sql_parse.cc:1266)
by: do_handle_one_connection (sql_connect.cc:1267)
by: handle_one_connection (sql_connect.cc:1181)
by: start_thread (pthread_create.c:309)
by: clone (clone.S:115)

Debug build asserts:

bool greedy_search(JOIN*, table_map, uint, uint): Assertion `!is_interleave_error' failed.

--source include/have_innodb.inc
 
drop table if exists y,e,j;
create table e(a int,unique key (a)) engine=innodb;
create table j(b int) engine=innodb;
create table y(a int,b int)engine=innodb;
set optimizer_prune_level=0;
set optimizer_search_depth=2;
select 1 from y join e a 
natural left join e b 
natural right outer join j;



 Comments   
Comment by Elena Stepanova [ 2013-03-13 ]

Could be a duplicate of, or related to, MDEV-621.

Comment by Sergei Petrunia [ 2013-05-04 ]

Added testcase

Comment by Sergei Petrunia [ 2013-05-04 ]

The problem itself was fixed by fix for MDEV-621

Generated at Thu Feb 08 06:55:07 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.