EXPLAIN FORMAT=JSON in MySQL

You are viewing an old version of this article. View the current version here.

This is a page for listing thing that we are not happy with in MySQL/Oracle's implementation of EXPLAIN FORMAT=JSON.

High priority

These will definitely be fixed

Join buffering doesn't show condition for buffered table

MySQL [dbt3sf1]> explain format=json select * from orders,customer where o_orderdate between '1995-01-01' and '1995-02-02' and c_acctbal <0 and o_custkey + 1 = c_custkey -1 \G

EXPLAIN: {
  "query_block": {
    "select_id": 1,
    "nested_loop": [
      {
        "table": {
          "table_name": "orders",
          "access_type": "range",
          "possible_keys": [
            "i_o_orderdate"
          ],
          "key": "i_o_orderdate",
          "used_key_parts": [
            "o_orderDATE"
          ],
          "key_length": "4",
          "rows": 40676,
          "filtered": 100,
          "index_condition": "(`dbt3sf1`.`orders`.`o_orderDATE` between '1995-01-01' and '1995-02-02')"
        }
      },
      {
        "table": {
          "table_name": "customer",
          "access_type": "ALL",
          "possible_keys": [
            "c_acctbal",
            "i_c_acctbal_nationkey"
          ],
          "rows": 149415,
          "filtered": 18.037,
          "using_join_buffer": "Block Nested Loop",
          "attached_condition": "((`dbt3sf1`.`customer`.`c_acctbal` < 0) and ((`dbt3sf1`.`orders`.`o_custkey` + 1) = (`dbt3sf1`.`customer`.`c_custkey` - 1)))"
        }
      }
    ]
  }
}

Nice to have

These do not have to be fixed, but are highly-desirable.

Smaller stuff

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.