[MDEV-18527] Optimizer trace for DELETE query shows table:null Created: 2019-02-09  Updated: 2019-02-13  Resolved: 2019-02-13

Status: Closed
Project: MariaDB Server
Component/s: Optimizer
Affects Version/s: 10.4
Fix Version/s: 10.4.3

Type: Bug Priority: Major
Reporter: Sergei Petrunia Assignee: Varun Gupta (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-6111 optimizer trace Closed

 Description   

create table ten(a int);
insert into ten values (0),(1),(2),(3),(4),(5),(6),(7),(8),(9);
create table t10 (a int, b int);
insert into t10 select a,a from ten;
alter table t10 add key(a);
 
set optimizer_trace=1;
explain delete from t10 where t10.a<3;
select * from information_schema.optimizer_trace\G 

prints

*************************** 1. row ***************************
                            QUERY: explain delete from t10 where t10.a<3
                            TRACE: {
  "steps": [
    {
      "table": null,
      "range_analysis": {
        "table_scan": {
          "rows": 10,
          "cost": 5.1
        },
        "potential_range_indexes": [



 Comments   
Comment by Varun Gupta (Inactive) [ 2019-02-13 ]

Fixed as part of MDEV-6111

Generated at Thu Feb 08 08:44:48 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.