Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL)
Description
INSERT ... SELECT statement does not produce optimizer trace:
create table t100 (a int, b int); |
create table t101 (a int, b int); |
insert into t101 select seq, seq from seq_1_to_1000; |
set optimizer_trace=1; |
insert into t100 select * from t101 where a<= b and a >4; |
MariaDB [test]> select * from information_schema.optimizer_trace\G
|
Empty set (0.002 sec)
|
It should produce it.
Attachments
Activity
The patch itself is ok. The testcase seems to large. The contents of the optimizer trace are actually irrelevant.
Please change
+select * from information_schema.optimizer_trace;
|
to something like
+select QUERY, LENGTH(trace)>1 from information_schema.optimizer_trace;
|
Ok to push after this is addressed.
Please review bb-10.5-mdev-29298.