explain.depesz.com

A tool for finding a real cause for slow queries.

Result: g7p

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

Sort (cost=2345.44..2385.55 rows=16044 width=52) (actual time=43.825..50.547 rows=16044 loops=1)

  • Sort Key: r.inventory_id, r.rental_date
  • Sort Method: external merge Disk: 1096kB
2. 13.471 22.711 ↑ 1.0 16044 1

Hash Join (cost=128.07..703.28 rows=16044 width=52) (actual time=4.345..22.711 rows=16044 loops=1)

  • Hash Cond: (r.inventory_id = i.inventory_id)
3. 4.913 4.913 ↑ 1.0 16044 1

Seq Scan on rental r (cost=0.00..294.44 rows=16044 width=36) (actual time=0.008..4.913 rows=16044 loops=1)

4. 2.311 4.327 ↑ 1.0 4581 1

Hash (cost=70.81..70.81 rows=4581 width=16) (actual time=4.327..4.327 rows=4581 loops=1)

  • Buckets: 1024 Batches: 1 Memory Usage: 162kB
5. 2.016 2.016 ↑ 1.0 4581 1

Seq Scan on inventory i (cost=0.00..70.81 rows=4581 width=16) (actual time=0.008..2.016 rows=4581 loops=1)