Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
-
None
Description
{format:sql}
CREATE TABLE t1 (id INT, value INT);
CREATE TABLE t2 (id INT);
PREPARE stmt FROM 'UPDATE t1 t1 SET value = (SELECT 1 FROM t2 WHERE id = t1.id)';
execute stmt;
insert into t1 values (1,10),(2,10),(3,10);
insert into t2 values (1),(2);
execute stmt; # <<=== Memory leak happens on running this statement
select * from t1;
deallocate prepare stmt;
DROP TABLE t1,t2;{format}
CREATE TABLE t1 (id INT, value INT);
CREATE TABLE t2 (id INT);
PREPARE stmt FROM 'UPDATE t1 t1 SET value = (SELECT 1 FROM t2 WHERE id = t1.id)';
execute stmt;
insert into t1 values (1,10),(2,10),(3,10);
insert into t2 values (1),(2);
execute stmt; # <<=== Memory leak happens on running this statement
select * from t1;
deallocate prepare stmt;
DROP TABLE t1,t2;{format}
The above use case doesn't show memory leaking on 10.11.
The similar issue could take place on running the DELETE statement with the LIMIT clause in PS/SP mode. So, this task also about fixing a memory leak in the code that processes the DELETE statement.
Attachments
Issue Links
- is part of
-
MDEV-14959 Control over memory allocated for SP/PS
-
- In Progress
-