explain.depesz.com

A tool for finding a real cause for slow queries.

Result: oU3

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

Limit (cost=10,413.93..10,413.96 rows=15 width=12) (actual time=23.217..23.219 rows=15 loops=1)

2. 0.559 23.216 ↑ 113.8 15 1

Sort (cost=10,413.93..10,418.19 rows=1,707 width=12) (actual time=23.216..23.216 rows=15 loops=1)

  • Sort Key: replays_game.game_time
  • Sort Method: top-N heapsort Memory: 25kB
3. 0.807 22.657 ↑ 1.3 1,289 1

Nested Loop (cost=7,914.79..10,372.05 rows=1,707 width=12) (actual time=16.305..22.657 rows=1,289 loops=1)

4. 1.462 16.694 ↓ 2.9 1,289 1

HashAggregate (cost=7,914.79..7,919.18 rows=439 width=4) (actual time=16.288..16.694 rows=1,289 loops=1)

5. 15.232 15.232 ↑ 1.3 1,289 1

Index Scan using replays_playeringame_player_id on replays_playeringame (cost=0.00..7,910.52 rows=1,707 width=4) (actual time=0.101..15.232 rows=1,289 loops=1)

  • Index Cond: (player_id = 50027)
  • Filter: ((win IS NOT NULL) AND (apm IS NOT NULL) AND (wpm IS NOT NULL) AND (apm > 0::double precision) AND (wpm > 0::double precision))
6. 5.156 5.156 ↑ 1.0 1 1,289

Index Scan using replays_game_pkey on replays_game (cost=0.00..5.57 rows=1 width=12) (actual time=0.004..0.004 rows=1 loops=1,289)

  • Index Cond: (id = replays_playeringame.game_id)