explain.depesz.com

A tool for finding a real cause for slow queries.

Result: H4j

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 0.000 0.000 ↓ 0.0

Hash Join (cost=100.14..17,764.92 rows=16,947 width=3,257) (actual time=.. rows= loops=)

  • Hash Cond: (pt.categ_id = pc.id)
2. 0.000 0.000 ↓ 0.0

Nested Loop (cost=0.00..17,530.76 rows=16,947 width=2,907) (actual time=.. rows= loops=)

3. 0.000 0.000 ↓ 0.0

Nested Loop (cost=0.00..10,405.68 rows=16,947 width=2,443) (actual time=.. rows= loops=)

4. 0.000 0.000 ↓ 0.0

Merge Join (cost=0.00..3,057.48 rows=16,947 width=2,035) (actual time=.. rows= loops=)

  • Merge Cond: (sp.id = sm.picking_id)
5. 0.000 0.000 ↓ 0.0

Index Scan using stock_picking_pkey on stock_picking sp (cost=0.00..363.51 rows=4,147 width=826) (actual time=.. rows= loops=)

6. 0.000 0.000 ↓ 0.0

Index Scan using stock_move_picking_id_index on stock_move sm (cost=0.00..5,726.72 rows=39,259 width=1,209) (actual time=.. rows= loops=)

7. 0.000 0.000 ↓ 0.0

Index Scan using product_product_pkey on product_product pp (cost=0.00..0.42 rows=1 width=408) (actual time=.. rows= loops=)

  • Index Cond: (pp.id = sm.product_id)
8. 0.000 0.000 ↓ 0.0

Index Scan using product_template_pkey on product_template pt (cost=0.00..0.41 rows=1 width=464) (actual time=.. rows= loops=)

  • Index Cond: (pt.id = pp.product_tmpl_id)
9. 0.000 0.000 ↓ 0.0

Hash (cost=1.06..1.06 rows=6 width=350) (actual time=.. rows= loops=)

10. 0.000 0.000 ↓ 0.0

Seq Scan on product_category pc (cost=0.00..1.06 rows=6 width=350) (actual time=.. rows= loops=)