Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
N/A
-
None
-
10.2.0-5
Description
delete_returning test fails in MDEV-8646 tree.
Crashing queries:
CREATE TABLE t1 (i1 int);
|
INSERT INTO t1 VALUES (1),(2);
|
CREATE TABLE t2 (i2 int);
|
INSERT INTO t2 VALUES (1),(2);
|
DELETE FROM t1 ORDER BY i1 RETURNING ( SELECT i2 FROM t2 );
|
The reason the last one crashes is that the execution code first calls:
JOIN::cleanup (this=0x7fff64065c68, full=true)
and then it calls
JOIN::exec (this=0x7fff64065c68)
that is, attempts to execute a join where it already did a cleanup.
Attachments
Issue Links
- is part of
-
MDEV-8646 Re-engineer the code for post-join operations
-
- Closed
-
- relates to
-
MDEV-13776 mysqld got signal 11 on delete returning
-
- Closed
-
Activity
Sprint | 10.2.0-5 [ 32 ] |
Affects Version/s | N/A [ 14700 ] |
Fix Version/s | 10.2 [ 14601 ] |
Fix Version/s | N/A [ 14700 ] | |
Fix Version/s | 10.2 [ 14601 ] | |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Link |
This issue relates to |
Workflow | MariaDB v3 [ 73821 ] | MariaDB v4 [ 150045 ] |
The "exec-after-cleanup" can be observed on MariaDB 10.0, too. It doesn't crash, because in 10.0, a join can survive JOIN::exec() after JOIN::cleanup(full=true).