Details
Description
Select from complex view using where clause gets SIGNAL 11 crash with derived_merge=on in versions 10.6 - 10.9. The issue does not happen in 10.5 or 10.10. If derived_merge=off then the issue does not happen. If derived_merge=on and there is no where clause used against the view, the issue does not happen. The statement below causes the issue every time when derived_merge=on.
A customer reported this and does not want to have to turn derived_merge off because they don't want to lose out on query performance. They noticed the issue after upgrading from 10.5 to 10.6. I tested out the other versions to verify the scope of the issue.
Recreation steps:
- Load the attached sql script to create the schema, and populate it with data
- Run the below select statement
This should returnERROR 2013 (HY000): Lost connection to server during query
In the error log it reports a SIGNAL 11.
SELECT this_.WORKFLOW_ID as y0_, this_.WORKFLOW_TYPE_ID as y1_, this_.COMPLETED_BY as y2_, this_.STATUS as y3_, this_.WORKFLOW as y4_, this_.WORKFLOW_NAME as y5_ |
FROM ABC_CAM_VW_WORKFLOW_TAB this_ |
WHERE this_.WORKFLOW_ID = 7 |
ORDER BY y0_ ASC |
LIMIT 1;
|
Attachments
Issue Links
- relates to
-
MDEV-27748 Split_materialized: Crash in best_access_path() while executing complex query
- Closed
-
MDEV-28901 SIGSEGV in optimize_keyuse on INSERT
- Closed
-
MDEV-30711 The mysqld service core occurs when the query statement executes the execution plan
- Confirmed