explain.depesz.com

A tool for finding a real cause for slow queries.

Result: 661

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 8.058 23.929 ↑ 1.0 4664 1

HashAggregate (cost=1320.07..1366.71 rows=4664 width=32) (actual time=23.394..23.929 rows=4664 loops=1)

2. 8.055 15.871 ↓ 1.0 18370 1

Hash Right Join (cost=264.94..1091.55 rows=18282 width=32) (actual time=5.449..15.871 rows=18370 loops=1)

  • Hash Cond: (pol.order_id = po.id)
3. 2.388 2.388 ↑ 1.0 18279 1

Seq Scan on purchase_order_line pol (cost=0.00..483.82 rows=18282 width=12) (actual time=0.005..2.388 rows=18279 loops=1)

4. 1.541 5.428 ↑ 1.0 4664 1

Hash (cost=206.64..206.64 rows=4664 width=24) (actual time=5.428..5.428 rows=4664 loops=1)

  • Buckets: 1024 Batches: 1 Memory Usage: 292kB
5. 3.887 3.887 ↑ 1.0 4664 1

Seq Scan on purchase_order po (cost=0.00..206.64 rows=4664 width=24) (actual time=0.021..3.887 rows=4664 loops=1)