explain.depesz.com

PostgreSQL's explain analyze made readable

Result: J7Rh : check rule query

Settings

Optimization(s) for this plan:

# exclusive inclusive rows x rows loops node
1. 0.003 0.267 ↑ 1.0 2 1

Nested Loop Left Join (cost=0.55..63.10 rows=2 width=678) (actual time=0.236..0.267 rows=2 loops=1)

2. 0.006 0.258 ↑ 1.0 2 1

Nested Loop Left Join (cost=0.42..62.75 rows=2 width=132) (actual time=0.230..0.258 rows=2 loops=1)

3. 0.230 0.230 ↑ 1.0 2 1

Seq Scan on rule_status rulestatus0_ (cost=0.00..45.75 rows=2 width=31) (actual time=0.211..0.230 rows=2 loops=1)

  • Filter: ((NOT is_deleted) AND (dms_complete_id = 1256))
  • Rows Removed by Filter: 2049
4. 0.006 0.022 ↑ 1.0 1 2

Nested Loop Left Join (cost=0.42..8.49 rows=1 width=101) (actual time=0.010..0.011 rows=1 loops=2)

5. 0.010 0.010 ↑ 1.0 1 2

Index Scan using rule_pkey on rule rule1_ (cost=0.28..8.29 rows=1 width=65) (actual time=0.004..0.005 rows=1 loops=2)

  • Index Cond: (rulestatus0_.rule_id = id)
6. 0.006 0.006 ↑ 1.0 1 2

Index Scan using doc_category_pkey on doc_category doccategor2_ (cost=0.14..0.20 rows=1 width=36) (actual time=0.003..0.003 rows=1 loops=2)

  • Index Cond: (rule1_.doc_cat_id = id)
7. 0.006 0.006 ↑ 1.0 1 2

Index Scan using product_type_pkey on product_type producttyp3_ (cost=0.13..0.17 rows=1 width=538) (actual time=0.002..0.003 rows=1 loops=2)

  • Index Cond: (rule1_.product_type_id = id)
Planning time : 0.359 ms
Execution time : 0.329 ms