Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.0.19, 10.0.25, 10.0(EOL), 10.1(EOL)
-
None
-
Identified on centos-release-6-5.el6.centos.11.2.x86_64 and centos-release-6-7.el6.centos.12.3.x86_64
-
10.0.26
Description
I understand this is generally a malformed query and a rather esoteric set of circumstances, but it was identified by accident by one of our developers.
Scenario: If an InnoDB column is indexed, and the query has a NOT IN with more than two parameters, one of which is "null", the database crashes. If the index isn't there, the database does not crash. If the table is not InnoDB, the database does not crash.
Test Case (verified on both 10.0.19 and 10.0.25 for Centos 6 x86_64 in both our development and production environments):
create table crash |
(col_a int(11), |
col_b varchar(10), |
key (col_b)) |
engine=innodb;
|
– Does not crash
select * |
from crash |
where col_b not in (null); |
– Does not crash
select * |
from crash |
where col_b not in (null, ''); |
– Does not crash
select * |
from crash |
where col_b not in ('', '0'); |
– Crash
select * |
from crash |
where col_b not in (null, '', 'A'); |
– Crash
select * |
from crash |
where col_b not in (null, '', '0'); |
Attachments
Issue Links
- duplicates
-
MDEV-10369 Simple select or explain crashes mariadb with signal 11 with NOT IN ( NULL , 'data' )
- Closed
- relates to
-
MDEV-10167 MariaDB crashes with Xen PVH - mysqld got signal 11
- Closed