explain.depesz.com

PostgreSQL's explain analyze made readable

Result: hWeS

Settings

Optimization(s) for this plan:

# exclusive inclusive rows x rows loops node
1. 0.000 0.000 ↓ 0.0

Subquery Scan on tt (cost=14,069.15..14,070.41 rows=14 width=23) (actual rows= loops=)

  • Filter: (tt.ranking <= 5)
2. 0.000 0.000 ↓ 0.0

WindowAgg (cost=14,069.15..14,069.89 rows=42 width=31) (actual rows= loops=)

3. 0.000 0.000 ↓ 0.0

Sort (cost=14,069.15..14,069.26 rows=42 width=23) (actual rows= loops=)

  • Sort Key: t.cnt DESC
4. 0.000 0.000 ↓ 0.0

Subquery Scan on t (cost=14,067.18..14,068.02 rows=42 width=23) (actual rows= loops=)

5. 0.000 0.000 ↓ 0.0

HashAggregate (cost=14,067.18..14,067.60 rows=42 width=23) (actual rows= loops=)

  • Group Key: crimes.analysis_neighborhood, count(*) OVER (?)
6. 0.000 0.000 ↓ 0.0

WindowAgg (cost=0.42..13,537.78 rows=105,880 width=23) (actual rows= loops=)

7. 0.000 0.000 ↓ 0.0

Index Only Scan using neighborhood_date on crimes (cost=0.42..11,949.58 rows=105,880 width=15) (actual rows= loops=)

  • Index Cond: (analysis_neighborhood IS NOT NULL)