explain.depesz.com

A tool for finding a real cause for slow queries.

Result: Ygz

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

Aggregate (cost=1355104.07..1355104.08 rows=1 width=4) (actual time=463974.350..463974.351 rows=1 loops=1)

2. 29.630 463974.000 ↓ 45.0 90 1

Hash Join (cost=2916.53..1355104.07 rows=2 width=4) (actual time=1589.469..463974.000 rows=90 loops=1)

  • Hash Cond: (listing1_.listingid = auction0_.fklistingid)
3. 106.995 463600.765 ↓ 13.2 8768 1

Nested Loop (cost=8.28..1352175.83 rows=666 width=4) (actual time=2.254..463600.765 rows=8768 loops=1)

4. 102045.689 463188.154 ↓ 11.3 12734 1

Hash Join (cost=8.28..1343357.06 rows=1130 width=4) (actual time=2.185..463188.154 rows=12734 loops=1)

  • Hash Cond: (listingadd2_.fkzipcodeid = zipcode3_.zipcodeid)
5. 361142.383 361142.383 ↓ 1.0 49328614 1

Seq Scan on address listingadd2_ (cost=0.00..1158373.44 rows=49323744 width=8) (actual time=0.033..361142.383 rows=49328614 loops=1)

6. 0.010 0.082 ↑ 1.0 1 1

Hash (cost=8.27..8.27 rows=1 width=4) (actual time=0.082..0.082 rows=1 loops=1)

  • Buckets: 1024 Batches: 1 Memory Usage: 1kB
7. 0.072 0.072 ↑ 1.0 1 1

Index Scan using idx_zipcode_zipcode on zipcode zipcode3_ (cost=0.00..8.27 rows=1 width=4) (actual time=0.070..0.072 rows=1 loops=1)

  • Index Cond: (zipcode = '32818'::text)
8. 305.616 305.616 ↑ 3.0 1 12734

Index Scan using idx_listing_fkbestaddressid on listing listing1_ (cost=0.00..7.77 rows=3 width=8) (actual time=0.019..0.024 rows=1 loops=12734)

  • Index Cond: (fkbestaddressid = listingadd2_.addressid)
9. 179.143 343.605 ↑ 1.0 91833 1

Hash (cost=1760.33..1760.33 rows=91833 width=8) (actual time=343.605..343.605 rows=91833 loops=1)

  • Buckets: 16384 Batches: 1 Memory Usage: 2512kB
10. 164.462 164.462 ↑ 1.0 91833 1

Seq Scan on auction auction0_ (cost=0.00..1760.33 rows=91833 width=8) (actual time=0.007..164.462 rows=91833 loops=1)