explain.depesz.com

A tool for finding a real cause for slow queries.

Result: aTI : books with join

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

HashAggregate (cost=2624.45..2696.83 rows=7238 width=17) (actual time=120.503..123.694 rows=7144 loops=1)

  • Output: a.name
  • Buffers: shared hit=756
2. 63.242 88.668 ↑ 1.0 7144 1

Hash Join (cost=1062.47..2606.36 rows=7238 width=17) (actual time=25.478..88.668 rows=7144 loops=1)

  • Output: a.name
  • Hash Cond: ((a.title)::text = (b.title)::text)
  • Buffers: shared hit=756
  • -> Seq Scan on stuff.author a (cost=0.00..909.00 rows=50000 width=34) (actual time=0.011..-5.664 rows=50000 loops=1)
  • Output: a.title, a.name
  • Buffers: shared hit=409
3. 0.000 25.426 ↑ 1.0 7144 1

Hash (cost=972.00..972.00 rows=7238 width=17) (actual time=25.426..25.426 rows=7144 loops=1)

  • Output: b.title
  • Buckets: 1024 Batches: 1 Memory Usage: 291kB
  • Buffers: shared hit=347
4. 191.696 191.696 ↑ 1.0 7144 1

Seq Scan on stuff.book b (cost=0.00..972.00 rows=7238 width=17) (actual time=0.017..191.696 rows=7144 loops=1)

  • Output: b.title
  • Filter: ((b.genre)::text = 'romance'::text)
  • Buffers: shared hit=347