[MDEV-4524] Server crashes when querying from multiple file CONNECT engine table Created: 2013-05-14  Updated: 2013-06-12  Resolved: 2013-06-12

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

Type: Bug Priority: Major
Reporter: Jens Dietze Assignee: Olivier Bertrand
Resolution: Fixed Votes: 0
Labels: connect-engine
Environment:

Centos 6.4



 Description   

Steps to reproduce:
1. create a csv-file /tmp/test1.csv, with the following content:
test;bla
2. create a csv-file /tmp/test2.csv with the following content:
test2;blub
3. create a table:

CREATE TABLE `test_all` (
  `a` char(10) DEFAULT NULL,
  `b` char(10) DEFAULT NULL
) ENGINE=CONNECT DEFAULT CHARSET=latin1 `table_type`=CSV `file_name`='/tmp/test*.csv' `sep_char`=';' `compress`=0 `multiple`=1
4. Query the table:
SELECT a FROM test_all;
-> ERROR 2013 (HY000): Lost connection to MySQL server during query

If you only use one file as source for your table, everything works as expected:

CREATE TABLE `test1` (
  `a` char(10) DEFAULT NULL,
  `b` char(10) DEFAULT NULL
) ENGINE=CONNECT DEFAULT CHARSET=latin1 `table_type`=CSV `file_name`='/tmp/test1.csv' `sep_char`=';' `compress`=0 `multiple`=0
SELECT a FROM test1;
+------+
| a    |
+------+
| test |
+------+

Excerpt from error log:

Server version: 10.0.2-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=1
max_threads=153
thread_count=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466436 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x0x288d158
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x7fbb52d84d78 thread_stack 0x48000
??:0(my_print_stacktrace)[0xad121e]
??:0(handle_fatal_signal)[0x6db20b]
??:0(??)[0x7fbb529b3500]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7fbb14004c40): is an invalid pointer
Connection ID (thread ID): 1
Status: NOT_KILLED
 
Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=off,exists_to_in=off



 Comments   
Comment by Olivier Bertrand [ 2013-06-12 ]

Was a gcc problem of stack smashing on Linux

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