[MDEV-13180] Unused left join causes server crash - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 5.5(EOL), 10.0(EOL), 10.1(EOL), 10.2(EOL)
Fix Version/s: 10.1.26, 5.5.57, 10.0.32, 10.2.8
Component/s: Data Manipulation - Subquery, Optimizer, Server
Labels:
None
Environment:
Ubuntu 14.04 and Official Docker containers

Description

The following queries cause a server crash for the latest versions of MariaDB from 5.5 to 10.3.

I've tested it against the TGZ version of 10.0.28 and the Docker versions of 5.5.56, 10.0.31, 10.1.24, 10.2.6, and 10.3.0.

It seems to be a MariaDB-specific issue as the same queries don't result in a crash in the Docker versions of MySQL 5.6 and 5.7 and Percona 5.6.

CREATE DATABASE IF NOT EXISTS `test`;

USE `test`;

CREATE TABLE

    `test1`

SELECT

CREATE TABLE

    `test2`

        `effdt` datetime NOT NULL,

        `column` enum('TEST') NOT NULL

INSERT INTO

    `test2`

    (`effdt`,`column`)

VALUES

    ('1900-01-01 00:00:00', 'TEST')

SELECT

FROM

    `test1` a

        LEFT JOIN

    `test2` b

ON

            b.`effdt` = (

                SELECT

                    MAX(b.`effdt`)

                FROM

                    `test2` b_t

                WHERE

                    b_t.`column` = b.`column`

docker-maria-5.5.56
Version: '5.5.56-MariaDB-1~wheezy' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
170626 20:45:09 [ERROR] mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 5.5.56-MariaDB-1~wheezy
key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=1
max_threads=102
thread_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759561 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fe72dc06000
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 = 0x7fe754f25e40 thread_stack 0x48000
mysqld(my_print_stacktrace+0x2b)[0x55c9428b521b]
mysqld(handle_fatal_signal+0x422)[0x55c9424ea382]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0)[0x7fe754b880a0]
mysqld(_ZN14Item_subselect30enumerate_field_refs_processorEPh+0x44)[0x55c9425636b4]
mysqld(_ZN20Dep_analysis_context27setup_equality_modules_depsEP4ListI10Dep_moduleE+0x13d)[0x55c94249bc2d]
mysqld(+0x4901a4)[0x55c94249c1a4]
mysqld(+0x4902ba)[0x55c94249c2ba]
mysqld(+0x3e7ba2)[0x55c9423f3ba2]
mysqld(_ZN4JOIN8optimizeEv+0x7c1)[0x55c9423f5a91]
mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0xd4)[0x55c9423f8044]
mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x2c3)[0x55c9423fee73]
mysqld(+0x39b4b1)[0x55c9423a74b1]
mysqld(_Z21mysql_execute_commandP3THD+0x1bcd)[0x55c9423aed2d]
mysqld(+0x3a7057)[0x55c9423b3057]
mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1b51)[0x55c9423b54e1]
mysqld(_Z24do_handle_one_connectionP3THD+0x22b)[0x55c94246bdeb]
mysqld(handle_one_connection+0x51)[0x55c94246be71]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50)[0x7fe754b7fb50]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fe75348bfbd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7fe72001f018): SELECT 1 FROM `test1` a LEFT JOIN `test2` b ON b.`effdt` = ( SELECT MAX(b.`effdt`) FROM `test2` b_t WHERE b_t.`column` = b.`column` )
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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains

docker-maria-10.0.31
Version: '10.0.31-MariaDB-1~jessie' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
170626 20:24:46 [ERROR] mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.0.31-MariaDB-1~jessie
key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=1
max_threads=102
thread_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759763 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f33c9ff5008
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 = 0x7f33f142be88 thread_stack 0x48000
mysqld(my_print_stacktrace+0x2e)[0xbc576e]
mysqld(handle_fatal_signal+0x3af)[0x73860f]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f33f108c890]
mysqld(_ZN14Item_subselect30enumerate_field_refs_processorEPh+0x28)[0x7bd4e8]
mysqld[0x6d4fad]
mysqld[0x6d51da]
mysqld[0x60f88a]
mysqld[0x617933]
mysqld(_ZN4JOIN8optimizeEv+0x11b)[0x61a08b]
mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0xa52)[0x61e022]
mysqld[0x5baa4b]
mysqld(_Z21mysql_execute_commandP3THD+0x4e3f)[0x5c673f]
mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x1ca)[0x5c83ba]
mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1559)[0x5c9ea9]
mysqld(_Z24do_handle_one_connectionP3THD+0x25b)[0x6993ab]
mysqld(handle_one_connection+0x39)[0x6993f9]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f33f1085064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f33ef68b62d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f33b9020020): SELECT 1 FROM `test1` a LEFT JOIN `test2` b ON b.`effdt` = ( SELECT MAX(b.`effdt`) FROM `test2` b_t WHERE b_t.`column` = b.`column` )
Connection ID (thread ID): 2
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=on,exists_to_in=on

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

docker-maria-10.1.24
Version: '10.1.24-MariaDB-1~jessie' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
170626 20:25:21 [ERROR] mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.1.24-MariaDB-1~jessie
key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=1
max_threads=102
thread_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759836 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7ff0b625a008
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 = 0x7ff0b983c1f8 thread_stack 0x48400
mysqld(my_print_stacktrace+0x2e)[0x564c0deacb1e]
mysqld(handle_fatal_signal+0x2fd)[0x564c0d9e55cd]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7ff0b94f2890]
mysqld(_ZN14Item_subselect30enumerate_field_refs_processorEPh+0x28)[0x564c0da68e68]
mysqld(_ZN20Dep_analysis_context27setup_equality_modules_depsEP4ListI10Dep_moduleE+0x132)[0x564c0d96b572]
mysqld(+0x52f4c5)[0x564c0d96c4c5]
mysqld(+0x52f5df)[0x564c0d96c5df]
mysqld(+0x46b19e)[0x564c0d8a819e]
mysqld(_ZN4JOIN14optimize_innerEv+0x7be)[0x564c0d8b068e]
mysqld(_ZN4JOIN8optimizeEv+0x29)[0x564c0d8b2f59]
mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x8ee)[0x564c0d8b38fe]
mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x141)[0x564c0d8b3ae1]
mysqld(+0x414b51)[0x564c0d851b51]
mysqld(_Z21mysql_execute_commandP3THD+0x5e83)[0x564c0d85dcc3]
mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x275)[0x564c0d860f35]
mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1c99)[0x564c0d8639d9]
mysqld(_Z10do_commandP3THD+0x14e)[0x564c0d8640fe]
mysqld(_Z24do_handle_one_connectionP3THD+0x182)[0x564c0d92fcd2]
mysqld(handle_one_connection+0x40)[0x564c0d92fe70]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7ff0b94eb064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7ff0b769562d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7ff07e421020): SELECT 1 FROM `test1` a LEFT JOIN `test2` b ON b.`effdt` = ( SELECT MAX(b.`effdt`) FROM `test2` b_t WHERE b_t.`column` = b.`column` )
Connection ID (thread ID): 2
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=on,exists_to_in=on,orderby_uses_equalities=off

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

docker-maria-10.2.6
Version: '10.2.6-MariaDB-10.2.6+maria~jessie' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
170626 20:28:56 [ERROR] mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.2.6-MariaDB-10.2.6+maria~jessie
key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=1
max_threads=102
thread_count=7
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759887 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fc9780009a8
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 = 0x7fc9c63bce38 thread_stack 0x49000
mysqld(my_print_stacktrace+0x2e)[0x5589d77b1a5e]
mysqld(handle_fatal_signal+0x305)[0x5589d71f24f5]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7fc9ebd3e890]
mysqld(_ZN14Item_subselect30enumerate_field_refs_processorEPv+0x28)[0x5589d7290d68]
mysqld(_ZN20Dep_analysis_context27setup_equality_modules_depsEP4ListI10Dep_moduleE+0x13b)[0x5589d716543b]
mysqld(+0x5eb42d)[0x5589d716642d]
mysqld(+0x5eb55f)[0x5589d716655f]
mysqld(+0x522bcb)[0x5589d709dbcb]
mysqld(_ZN4JOIN14optimize_innerEv+0xa25)[0x5589d70a5365]
mysqld(_ZN4JOIN8optimizeEv+0x33)[0x5589d70a7943]
mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x8bc)[0x5589d70aa0ec]
mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x137)[0x5589d70aa307]
mysqld(+0x4caf7e)[0x5589d7045f7e]
mysqld(_Z21mysql_execute_commandP3THD+0x4dca)[0x5589d705127a]
mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x28a)[0x5589d705444a]
mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x1cf3)[0x5589d7056e53]
mysqld(_Z10do_commandP3THD+0x164)[0x5589d70576f4]
mysqld(_Z24do_handle_one_connectionP7CONNECT+0x232)[0x5589d7129e72]
mysqld(handle_one_connection+0x3d)[0x5589d712a00d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7fc9ebd37064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc9ea11962d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7fc97800ef10): SELECT 1 FROM `test1` a LEFT JOIN `test2` b ON b.`effdt` = ( SELECT MAX(b.`effdt`) FROM `test2` b_t WHERE b_t.`column` = b.`column` )
Connection ID (thread ID): 8
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=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

docker-maria-10.3.0
Version: '10.3.0-MariaDB-10.3.0+maria~jessie' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
170626 22:21:44 [ERROR] mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.3.0-MariaDB-10.3.0+maria~jessie
key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=1
max_threads=102
thread_count=7
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759906 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f7c040009a8
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 = 0x7f7c78188e38 thread_stack 0x49000
mysqld(my_print_stacktrace+0x2e)[0x557336b8818e]
mysqld(handle_fatal_signal+0x305)[0x5573365b6405]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f7c8210a890]
mysqld(_ZN14Item_subselect30enumerate_field_refs_processorEPv+0x28)[0x55733665c5d8]
mysqld(_ZN20Dep_analysis_context27setup_equality_modules_depsEP4ListI10Dep_moduleE+0x13b)[0x55733650209b]
mysqld(+0x61608d)[0x55733650308d]
mysqld(+0x6161bf)[0x5573365031bf]
mysqld(+0x54c07b)[0x55733643907b]
mysqld(_ZN4JOIN14optimize_innerEv+0xa25)[0x557336440865]
mysqld(_ZN4JOIN8optimizeEv+0x33)[0x557336442e13]
mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x8bc)[0x55733644555c]
mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x139)[0x557336445779]
mysqld(+0x4f30ee)[0x5573363e00ee]
mysqld(_Z21mysql_execute_commandP3THD+0x6276)[0x5573363ecf96]
mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x351)[0x5573363f0481]
mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x2708)[0x5573363f3a48]
mysqld(_Z10do_commandP3THD+0x160)[0x5573363f4330]
mysqld(_Z24do_handle_one_connectionP7CONNECT+0x232)[0x5573364c6602]
mysqld(handle_one_connection+0x3d)[0x5573364c679d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f7c82103064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f7c804e562d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f7c0400f0e0): SELECT 1 FROM `test1` a LEFT JOIN `test2` b ON b.`effdt` = ( SELECT MAX(b.`effdt`) FROM `test2` b_t WHERE b_t.`column` = b.`column` )
Connection ID (thread ID): 8
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=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

Attachments

Issue Links

relates to

MDEV-7826 Server crashes in Item_subselect::enumerate_field_refs_processor

Closed

Activity

People

Assignee:: Sergei Golubchik

Reporter:: Eric P

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 2017-06-26 22:15

Updated:: 2017-07-12 16:55

Resolved:: 2017-07-12 16:54

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.