为什么我的PostgreSQL计划中的行数为0?

时间:2012-04-18 10:54:07

标签: database postgresql sql-execution-plan

我有一个查询,它使用嵌套循环等同连接两个表,TableA和TableB。由于“equi”-join约束,结果中返回的所有行因此将对应于来自这两个表中的每一个的至少一行。但是,根据计划(EXPLAIN ANALYZE),即使在最终结果中返回了一行,实际行数也是TableB中的0。 实际行在这里如何计算等于零?

这是执行计划:

=> explain analyze select p.id, p.title, s.count from products p, stock s where p.id = s.p_id and s.w_id = 6 and p.type = 9 and s.count > 0 order by p.title;
                                                          QUERY PLAN                                                          
------------------------------------------------------------------------------------------------------------------------------
 Sort  (cost=42.42..42.42 rows=2 width=36) (actual time=0.198..0.199 rows=1 loops=1)
   Sort Key: p.title
   Sort Method: quicksort  Memory: 25kB
   ->  Nested Loop  (cost=0.00..42.41 rows=2 width=36) (actual time=0.170..0.181 rows=1 loops=1)
         ->  Seq Scan on products p  (cost=0.00..9.25 rows=4 width=32) (actual time=0.068..0.106 rows=4 loops=1)
               Filter: (type = 9)
         ->  Index Scan using stock_pk on stock s  (cost=0.00..8.28 rows=1 width=8) (actual time=0.015..0.015 rows=0 loops=4)
               Index Cond: ((w_id = 6) AND (p_id = p.id))
               Filter: (count > 0)
 Total runtime: 0.290 ms

两个表定义......产品表首先:

=> \d products
           Table "public.products"
 Column |          Type          | Modifiers 
--------+------------------------+-----------
 id     | integer                | not null
 title  | character varying(100) | 
 type   | integer                | 
 price  | double precision       | 
 filler | character(500)         | 
Indexes:
    "products_pkey" PRIMARY KEY, btree (id)
    "products_type_idx" btree (type)
Referenced by:
    TABLE "orderline" CONSTRAINT "orderline_p_id_fkey" FOREIGN KEY (p_id) REFERENCES products(id)
    TABLE "stock" CONSTRAINT "stock_p_id_fkey" FOREIGN KEY (p_id) REFERENCES products(id)

股票表:

=> \d stock
     Table "public.stock"
 Column |  Type   | Modifiers 
--------+---------+-----------
 w_id   | integer | not null
 p_id   | integer | not null
 count  | integer | 
Indexes:
    "stock_pk" PRIMARY KEY, btree (w_id, p_id)
    "stock_p_id_idx" btree (p_id)
Foreign-key constraints:
    "stock_p_id_fkey" FOREIGN KEY (p_id) REFERENCES products(id)
    "stock_w_id_fkey" FOREIGN KEY (w_id) REFERENCES warehouses(id)

1 个答案:

答案 0 :(得分:4)

内部索引扫描的实际行是每次调用时返回的平均行数。

查看http://www.postgresql.org/docs/current/static/using-explain.html

  

在某些查询计划中,子计划节点可能会被执行多次。例如,在上面的嵌套循环计划中,每个外行执行一次内部索引扫描。在这种情况下,循环值报​​告节点的总执行次数,显示的实际时间和行值是每次执行的平均值。这样做是为了使数字与成本估算的显示方式相当。乘以循环值,得到节点中实际花费的总时间。

我不确定它是如何舍入的(我在平均后猜测到最接近的int),但可能是products中的大多数行没有&#39 ; t在stock中有相应的行。