explain.depesz.com

A tool for finding a real cause for slow queries.

Result: kQH

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

Aggregate (cost=540662.19..540662.20 rows=1 width=4) (actual time=3699.674..3699.674 rows=1 loops=1)

2. 336.922 3681.851 ↑ 2.6 51580 1

Hash Join (cost=16006.95..540331.11 rows=132430 width=4) (actual time=365.121..3681.851 rows=51580 loops=1)

  • Hash Cond: (l.fklistingstatusid = ls.listingstatusid)
3. 3114.406 3344.917 ↓ 1.0 802737 1

Bitmap Heap Scan on listing l (cost=16005.86..536026.05 rows=794580 width=8) (actual time=327.981..3344.917 rows=802737 loops=1)

  • Recheck Cond: (fklistingsourceid = 5027)
4. 230.511 230.511 ↓ 1.1 909198 1

Bitmap Index Scan on idx_listing_fklistingsourceid (cost=0.00..15807.21 rows=794580 width=0) (actual time=230.511..230.511 rows=909198 loops=1)

  • Index Cond: (fklistingsourceid = 5027)
5. 0.004 0.012 ↑ 1.0 1 1

Hash (cost=1.07..1.07 rows=1 width=4) (actual time=0.012..0.012 rows=1 loops=1)

  • Buckets: 1024 Batches: 1 Memory Usage: 1kB
6. 0.008 0.008 ↑ 1.0 1 1

Seq Scan on listingstatus ls (cost=0.00..1.07 rows=1 width=4) (actual time=0.006..0.008 rows=1 loops=1)

  • Filter: (shortname = 'active'::text)