[MDEV-4347] PBXT: Server crashes in handler::compare_key on SELECT .. FOR UPDATE Created: 2013-04-01  Updated: 2013-12-28  Resolved: 2013-12-28

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 5.1.67
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: pbxt

Issue Links:
Relates

 Description   

#3  <signal handler called>
#4  0x0000000000958350 in handler::compare_key (this=0x7f928041c6a0, range=0xa5a5a5a5a5a5a5a5) at handler.cc:4436
#5  0x0000000000cc6bd3 in ha_pbxt::xt_index_in_range (this=0x7f928041c6a0, ind=0x7f9280418628, search_key=0x0, buf=0x7f928041c890 "\374\376\376\376\376bar         \245\245\245\245\245\245\245\375\002") at ha_pbxt.cc:3028
#6  0x0000000000cc6dc7 in ha_pbxt::xt_index_next_read (this=0x7f928041c6a0, ot=0x7f928041d008, ind=0x7f9280418628, key_only=1, search_key=0x0, buf=0x7f928041c890 "\374\376\376\376\376bar         \245\245\245\245\245\245\245\375\002") at ha_pbxt.cc:3052
#7  0x0000000000cc8cad in ha_pbxt::index_first (this=0x7f928041c6a0, buf=0x7f928041c890 "\374\376\376\376\376bar         \245\245\245\245\245\245\245\375\002") at ha_pbxt.cc:3636
#8  0x0000000000830740 in join_read_first (tab=0x7f9260003070) at sql_select.cc:12574
#9  0x000000000082d38a in sub_select (join=0x7f92600075d8, join_tab=0x7f9260003070, end_of_records=false) at sql_select.cc:11779
#10 0x000000000082c9e3 in do_select (join=0x7f92600075d8, fields=0x425a338, table=0x0, procedure=0x0) at sql_select.cc:11532
#11 0x0000000000807917 in JOIN::exec (this=0x7f92600075d8) at sql_select.cc:2361
#12 0x0000000000808726 in mysql_select (thd=0x4258068, rref_pointer_array=0x425a400, tables=0x7f92600071e0, wild_num=0, fields=..., conds=0x0, og_num=0, order=0x0, group=0x0, having=0x0, proc_param=0x0, select_options=2147764736, result=0x7f92600075b8, unit=0x4259e00, select_lex=0x425a228) at sql_select.cc:2576
#13 0x00000000007fb8cb in handle_select (thd=0x4258068, lex=0x4259d60, result=0x7f92600075b8, setup_tables_done_option=0) at sql_select.cc:280
#14 0x0000000000752f65 in execute_sqlcom_select (thd=0x4258068, all_tables=0x7f92600071e0) at sql_parse.cc:5247
#15 0x0000000000743a96 in mysql_execute_command (thd=0x4258068) at sql_parse.cc:2386
#16 0x0000000000757188 in mysql_parse (thd=0x4258068, rawbuf=0x7f9260006ff0 "SELECT c FROM t1 FOR UPDATE", length=27, found_semicolon=0x7f9284e16900) at sql_parse.cc:6222
#17 0x000000000073f820 in dispatch_command (command=COM_QUERY, thd=0x4258068, packet=0x425b3e9 "", packet_length=27) at sql_parse.cc:1294
#18 0x000000000073dd17 in do_command (thd=0x4258068) at sql_parse.cc:906
#19 0x0000000000738667 in handle_one_connection (arg=0x4258068) at sql_connect.cc:1238
#20 0x00007f929ad8ee9a in start_thread (arg=0x7f9284e17700) at pthread_create.c:308
#21 0x00007f929aabbcbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112

revision-id: sergii@pisem.net-20130320202051-m8qdk6zvcci9vr5s
revno: 3194
branch-nick: 5.1

built with BUILD/compile-pentium-debug-max-no-ndb

Could not reproduce on 5.2 or 5.5.

Test case:

--source include/have_pbxt.inc
 
CREATE TABLE t1 (pk INT PRIMARY KEY, c CHAR(12), KEY(c)) ENGINE=PBXT;
INSERT INTO t1 VALUES (1,'foo'),(2,'bar');
 
BEGIN;
UPDATE t1 SET c = 'foobar';
 
--connect (con1,localhost,root,,test)
EXPLAIN EXTENDED SELECT c FROM t1 FOR UPDATE;
--send
  SELECT c FROM t1 FOR UPDATE;
 
--connection default
COMMIT;
 
--connection con1
--reap



 Comments   
Comment by Elena Stepanova [ 2013-04-01 ]

This one of course is not going to be fixed (both because it's PBXT and 5.1-only), but at least it will be searchable in the bug base.

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