explain.depesz.com

A tool for finding a real cause for slow queries.

Result: Uod

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

Sort (cost=79.14..79.64 rows=200 width=125) (actual time=6.775..6.971 rows=200 loops=1)

  • Sort Key: financeoperations.date
  • Sort Method: quicksort Memory: 78kB
2. 1.516 6.380 ↑ 1.0 200 1

Hash Join (cost=37.75..71.50 rows=200 width=125) (actual time=3.766..6.380 rows=200 loops=1)

  • Hash Cond: (partners.id = financeoperations.partner_id)
3. 1.180 1.180 ↑ 1.0 1,000 1

Seq Scan on partners (cost=0.00..28.00 rows=1,000 width=105) (actual time=0.009..1.180 rows=1,000 loops=1)

4. 0.307 3.684 ↑ 1.0 200 1

Hash (cost=35.25..35.25 rows=200 width=28) (actual time=3.684..3.684 rows=200 loops=1)

  • Buckets: 1024 Batches: 1 Memory Usage: 12kB
5. 1.540 3.377 ↑ 1.0 200 1

Hash Join (cost=12.50..35.25 rows=200 width=28) (actual time=0.656..3.377 rows=200 loops=1)

  • Hash Cond: (financeoperations.goodsoperation_id = goodsoperations.id)
6. 1.216 1.216 ↑ 1.0 1,000 1

Seq Scan on financeoperations (cost=0.00..17.00 rows=1,000 width=24) (actual time=0.008..1.216 rows=1,000 loops=1)

7. 0.298 0.621 ↑ 1.0 200 1

Hash (cost=10.00..10.00 rows=200 width=12) (actual time=0.621..0.621 rows=200 loops=1)

  • Buckets: 1024 Batches: 1 Memory Usage: 9kB
8. 0.323 0.323 ↑ 1.0 200 1

Seq Scan on goodsoperations (cost=0.00..10.00 rows=200 width=12) (actual time=0.008..0.323 rows=200 loops=1)