MySQL Execution Plan--IN子查詢包含超多值引發的查詢異常1

阿新 • • 發佈：2019-04-23

pos cos table HERE lock code 5.1 pic key

=======================================================================

SQL語句：

SELECT wave_no,
SUM(IF(picking_qty IS NULL, 0, picking_qty)) AS PICKED_QTY,
SUM(IF(differ_qty IS NULL, 0, differ_qty)) AS PICKED_DIFFER_QTY,
SUM(IF(relocate_qty IS NULL, 0, relocate_qty)) AS PICKED_RELOCATE_QTY FROM picking_locate_d
WHERE  yn  
= 0
AND CONCAT(wave_no,‘‘) IN
(
‘BC76361213164811‘,
‘BC76361213164810‘,
‘BC76361213154684‘,
‘BC76361213155125‘
)
AND org_No= ‘661‘
AND distribute_No = ‘763‘
AND warehouse_No = ‘612‘
GROUP BY wave_no

執行計劃：

+----+-------------+------------------+------------+-------+---------------+-------------+---------+------+----------+----------+-------------+
| id | select_type | table            | partitions | type  | possible_keys | key         | key_len | ref 
  | rows     | filtered | Extra       |
+----+-------------+------------------+------------+-------+---------------+-------------+---------+------+----------+----------+-------------+
|  1 | SIMPLE      | picking_locate_d | NULL       | index | idx_wave_no   | idx_wave_no | 153     | NULL | 37541282 
 |     0.01 | Using where |
+----+-------------+------------------+------------+-------+---------------+-------------+---------+------+----------+----------+-------------+

執行計劃JSON：

EXPLAIN: {
  "query_block": {
    "select_id": 1,
    "cost_info": {
      "query_cost": "9549155.40"
    },
    "grouping_operation": {
      "using_filesort": false,
      "table": {
        "table_name": "picking_locate_d",
        "access_type": "index",
        "possible_keys": [
          "idx_wave_no"
        ],
        "key": "idx_wave_no",
        "used_key_parts": [
          "wave_no"
        ],
        "key_length": "153",
        "rows_examined_per_scan": 37522447,
        "rows_produced_per_join": 3752,
        "filtered": "0.01",
        "cost_info": {
          "read_cost": "9548404.95",
          "eval_cost": "750.45",
          "prefix_cost": "9549155.40",
          "data_read_per_join": "22M"
        },
        "used_columns": [
          "id",
          "wave_no",
          "picking_qty",
          "differ_qty",
          "relocate_qty",
          "org_no",
          "distribute_no",
          "warehouse_no",
          "yn"
        ],
        "attached_condition": "(
            (`report`.`picking_locate_d`.`yn` = 0) 
            and (concat(`report`.`picking_locate_d`.`wave_no`,‘‘) in (‘BC76361213164811‘,‘BC76361213164810‘,‘BC76361213154684‘,‘BC76361213155125‘)) 
            and (`report`.`picking_locate_d`.`org_no` = ‘661‘) 
            and (`report`.`picking_locate_d`.`distribute_no` = ‘763‘) 
            and (`report`.`picking_locate_d`.`warehouse_no` = ‘612‘)
        )"
      }
    }
  }
}

=======================================================================

SQL語句

SELECT wave_no,
SUM(IF(picking_qty IS NULL, 0, picking_qty)) AS PICKED_QTY,
SUM(IF(differ_qty IS NULL, 0, differ_qty)) AS PICKED_DIFFER_QTY,
SUM(IF(relocate_qty IS NULL, 0, relocate_qty)) AS PICKED_RELOCATE_QTY FROM picking_locate_d
WHERE  yn = 0
AND wave_no IN
(
‘BC76361213164811‘,
‘BC76361213164810‘,
‘BC76361213154684‘,
‘BC76361213155125‘
)
## AND org_No= ‘661‘
AND distribute_No = ‘763‘
AND warehouse_No = ‘612‘
GROUP BY wave_no;

執行計劃：

+----+-------------+------------------+------------+-------+---------------+-------------+---------+------+----------+----------+-------------+
| id | select_type | table            | partitions | type  | possible_keys | key         | key_len | ref  | rows     | filtered | Extra       |
+----+-------------+------------------+------------+-------+---------------+-------------+---------+------+----------+----------+-------------+
|  1 | SIMPLE      | picking_locate_d | NULL       | index | idx_wave_no   | idx_wave_no | 153     | NULL | 37541843 |     0.01 | Using where |
+----+-------------+------------------+------------+-------+---------------+-------------+---------+------+----------+----------+-------------+

執行計劃JSON

EXPLAIN: {
  "query_block": {
    "select_id": 1,
    "cost_info": {
      "query_cost": "38400.01"
    },
    "grouping_operation": {
      "using_filesort": false,
      "table": {
        "table_name": "picking_locate_d",
        "access_type": "range",
        "possible_keys": [
          "idx_wave_no"
        ],
        "key": "idx_wave_no",
        "used_key_parts": [
          "wave_no"
        ],
        "key_length": "153",
        "rows_examined_per_scan": 16000,
        "rows_produced_per_join": 15,
        "filtered": "0.10",
        "index_condition": "(
            (`report`.`picking_locate_d`.`wave_no` in (‘BC76361213164811‘,‘BC76361213164810‘,‘BC76361213154684‘,‘BC76361213155125‘)) 
            and (`report`.`picking_locate_d`.`distribute_no` = ‘763‘) 
            and (`report`.`picking_locate_d`.`warehouse_no` = ‘612‘)
        )",
        "cost_info": {
          "read_cost": "38396.81",
          "eval_cost": "3.20",
          "prefix_cost": "38400.01",
          "data_read_per_join": "98K"
        },
        "used_columns": [
          "id",
          "wave_no",
          "picking_qty",
          "differ_qty",
          "relocate_qty",
          "org_no",
          "distribute_no",
          "warehouse_no",
          "yn"
        ],
        "attached_condition": "(`report`.`picking_locate_d`.`yn` = 0)"
      }
    }
  }
}

=======================================================================

SQL語句：

SELECT wave_no,
SUM(IF(picking_qty IS NULL, 0, picking_qty)) AS PICKED_QTY,
SUM(IF(differ_qty IS NULL, 0, differ_qty)) AS PICKED_DIFFER_QTY,
SUM(IF(relocate_qty IS NULL, 0, relocate_qty)) AS PICKED_RELOCATE_QTY FROM picking_locate_d
WHERE  yn = 0
AND wave_no IN
(
‘BC76361213164811‘,
‘BC76361213164810‘,
‘BC76361213154684‘,
‘BC76361213155125‘
)
AND org_No= ‘661‘
AND distribute_No = ‘763‘
AND warehouse_No = ‘612‘
GROUP BY wave_no;

執行計劃：

+----+-------------+------------------+------------+-------+---------------+-------------+---------+------+-------+----------+------------------------------------+
| id | select_type | table            | partitions | type  | possible_keys | key         | key_len | ref  | rows  | filtered | Extra                              |
+----+-------------+------------------+------------+-------+---------------+-------------+---------+------+-------+----------+------------------------------------+
|  1 | SIMPLE      | picking_locate_d | NULL       | range | idx_wave_no   | idx_wave_no | 153     | NULL | 16000 |     0.10 | Using index condition; Using where |
+----+-------------+------------------+------------+-------+---------------+-------------+---------+------+-------+----------+------------------------------------+

執行計劃JOSN：

EXPLAIN: {
  "query_block": {
    "select_id": 1,
    "cost_info": {
      "query_cost": "9548371.80"
    },
    "grouping_operation": {
      "using_filesort": false,
      "table": {
        "table_name": "picking_locate_d",
        "access_type": "index",
        "possible_keys": [
          "idx_wave_no"
        ],
        "key": "idx_wave_no",
        "used_key_parts": [
          "wave_no"
        ],
        "key_length": "153",
        "rows_examined_per_scan": 37518548,
        "rows_produced_per_join": 1875,
        "filtered": "0.01",
        "cost_info": {
          "read_cost": "9547996.61",
          "eval_cost": "375.19",
          "prefix_cost": "9548371.80",
          "data_read_per_join": "11M"
        },
        "used_columns": [
          "id",
          "wave_no",
          "picking_qty",
          "differ_qty",
          "relocate_qty",
          "org_no",
          "distribute_no",
          "warehouse_no",
          "yn"
        ],
        "attached_condition": "(
            (`report`.`picking_locate_d`.`yn` = 0) 
            and (`report`.`picking_locate_d`.`wave_no` in (‘BC76361213164811‘,‘BC76361213164810‘,‘BC76361213155124‘,‘BC76361213154684‘,‘BC76361213155125‘)) 
            and (`report`.`picking_locate_d`.`org_no` = ‘661‘) 
            and (`report`.`picking_locate_d`.`distribute_no` = ‘763‘) 
            and (`report`.`picking_locate_d`.`warehouse_no` = ‘612‘)
        )"
      }
    }
  }
}

MySQL Execution Plan--IN子查詢包含超多值引發的查詢異常1

pos cos table HERE lock code 5.1 pic key ======================================================================= SQL語句： SELECT wave_n

MySQL Execution Plan--NOT EXISTS子查詢優化

次數 .com HERE 毫秒存在數據統計圖片兩個在很多業務場景中，會使用NOT EXISTS語句來確保返回數據不存在於特定集合，部分場景下NOT EXISTS語句性能較差，網上甚至存在謠言"NOT EXISTS無法走索引"。首先需要明確的是：索引不是萬能的

mysql查詢語句和多表關聯查詢以及子查詢

另一個多表 uri 多條件排序 image 毫無表連接 exist 原文地址: http://blog.csdn.net/github_37767025/article/details/67636061 1.查詢一張表： select * from 表名；

mysql（三）：mysql查詢語句和多表關聯查詢以及子查詢

1.查詢一張表：select * from 表名； 2.查詢指定欄位：select 欄位1，欄位2，欄位3....from 表名； 3.where條件查詢：select 欄位1，欄位2，欄位3 frome 表名 where 條件表示式；例：select *

多值模糊查詢報表的制作

程序字段名 text 遇到 ODB 模板區域 one ima 在數據查詢系統中，經常會涉及到模糊查詢和多值查詢。對於模糊查詢，我們可能都有所了解。就是根據用戶在參數框中輸入的關鍵字進行模糊匹配，這在SQL中是通過like條件實現的。而多值查詢則大多是一次在參數框中輸入2

眼睜睜地踩到 MySQL in 子查詢的“坑”

前言 MySQL是專案中常用的資料庫，其中in查詢也是很常用。最近專案除錯過程中，遇到一個出乎意料的select查詢，竟然用了33秒！一、表結構 1. userinfo 表 2. article 表二、問題SQL例項 select*fromuserinfowhereidin(selectau

警惕 MySql 更新 sql 的 WHERE 從句中的 IN() 子查詢時出現的效能陷阱

mer_stage 表有 216423 條記錄，DDL：CREATE TABLE `mer_stage` ( `STAGE_ID` int(11) NOT NULL AUTO_INCREMENT, `MER_ID` int(11) NOT NULL, `MER_C

mysql in 子查詢效率慢優化（轉）

現在的CMS系統、部落格系統、BBS等都喜歡使用標籤tag作交叉連結，因此我也嚐鮮用了下。但用了後發現我想查詢某個tag的文章列表時速度很慢，達到5秒之久！百思不解(後來終於解決)，我的表結構是下面這樣的，文章只有690篇。文章表article(id,title,content) 標籤表tag(tid,

MySQL IN子查詢

近日通過《mysql技術內幕：SQL程式設計》學習mysql子查詢，書中介紹了IN子查詢存在的問題，並且提供了一些優化方法。我在此書的基礎上進行了深入研究，總結幾點。 MySql優化器對IN子查詢優化時存在一個問題，MySql優化器對於IN語句的優化是“LAZY”的。對於I

包含IN子查詢的SQL語句的優化

當SQL語句中包含in語句時,有時候會極大的影響效能,我們可以把in子查詢用exists子查詢或外連線替代例子如下: 1.SQL語句中包含IN子查詢: Sql程式碼 SQL> select * from servers s 2 w

mysql not in子查詢返回結果為空

今天寫sql語句的時候，希望通過not in子查詢來限制查詢結果，實際SQL語句如下： select ID as id, TYPE_CODE as typeCode , TYPE_NAME as typeName , PARENT_ID as parentsId

mysql 數據操作子查詢帶比較運算符的子查詢

mys 比較運算 ack 員工 pre family employ 思路 weight 帶比較運算符的子查詢 #比較運算符：=、!=、>、>=、<、<=、<> #查詢大於所有人平均年齡的員工名與年齡思路先拿到所有人的平均年齡

mysql 數據操作子查詢介紹

!= 結果 span 子查詢 tro 運算符 mysql sql 嵌套子查詢就是：把一條sql語句放在一個括號裏，當做另外一條sql語句查詢條件使用拿到這個結果以後當做下一個sql語句查詢條件mysql 數據操作子查詢 #1：子查詢是將一個查詢語句嵌

mysql查詢包含某個字元的記錄

從excel匯入資料庫的時候,發現poi自動把電話號碼轉換為科學計數法了所以要把帶e的篩選出來 SELECT * FROM t_customer WHERE phone like '%E%'; 然後刪除 DELETE FROM t_customer WHERE phone LIKE

Mysql查詢語句——多表關聯查詢、子查詢

1.查詢一張表： select * from 表名； 2.查詢指定欄位：select 欄位1，欄位2，欄位3….from 表名； 3.where條件查詢：select 欄位1，欄位2，欄位3 frome 表名 where 條件表示式；例：select

mysql在把子查詢結果作為刪除表中資料的條件，mysql不允許在子查詢的同時刪除原表資料

** 目標表和原表一致 MYSQL不支援如此操作資料庫不能邊查詢邊刪除 ** delete from push_msg_overview where id in ( select id from push_msg_overview where pus

mysql資料庫模糊查詢(包含特使字元時)

mysql裡查詢 json 資料 1.mysql裡有個欄位儲存的是json格式的資料， 2.現在需要從頁面傳遞引數到php再進行搜尋匹配關鍵字， 3.將關鍵字頁json_encode後，去like匹配這個欄位，匹配不到解決方案： 1.只針對中文搜尋，存的資料一

MySQL開發技巧第二禪（子查詢中匹配兩個值、解決同屬性多值過濾的問題、計算累進稅的問題）

一、如何在子查詢中匹配兩個值 mysql子查詢的使用場景及其好處 1、什麼是子查詢？

mysql 欄位以逗號隔開查詢包含的的問題

解決的問題看截圖,這個表裡面的rid是逗號隔開的,需要查詢rid的任何一個值在 (1,2,3)內測試資料 CREATE TABLE `test` ( `rid` varchar(1024) DEFAULT NULL, `id` int(10) unsigne

mysql 子查詢（六）之主查詢和子查詢的執行順序

那麼，什麼是相關子查詢呢？舉個例子，查詢員工表中薪水大於本部門平均薪水的員工。首先構建思路，說到底還是查詢員工，所以主查詢是查詢員工，然後在where後面增加子查詢，查詢薪水大於本部門平均薪水。開始寫sql，如下：問題來了，查詢某個部門的薪水，公司有很多個部門，所以引數不能寫

MySQL Execution Plan--IN子查詢包含超多值引發的查詢異常1

相關推薦