explain.depesz.com

A tool for finding a real cause for slow queries.

Result: Jxg

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=203403.14..17764.92 rows=16947 width=3257) (actual time=.. rows= loops=)

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

Nested Loop (cost=34342.00..17530.76 rows=16947 width=2907) (actual time=.. rows= loops=)

3. 0.000 0.000 ↓ 0.0

Nested Loop (cost=434234.00..10405.68 rows=16947 width=2443) (actual time=.. rows= loops=)

4. 0.000 0.000 ↓ 0.0

Merge Join (cost=3243242.00..3057.48 rows=16947 width=2035) (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=3432423.00..363.51 rows=4147 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=3242342.00..5726.72 rows=39259 width=1209) (actual time=.. rows= loops=)

7. 0.000 0.000 ↓ 0.0

Index Scan using product_product_pkey on product_product pp (cost=23423423.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=32423432.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=23423423.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=324234234.00..1.06 rows=6 width=350) (actual time=.. rows= loops=)