explain.depesz.com

A tool for finding a real cause for slow queries.

Result: Y0w

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

Limit (cost=0.00..1,772.53 rows=15 width=12) (actual time=1,046.914..1,055.294 rows=15 loops=1)

2. 141.281 1,055.285 ↑ 61.3 15 1

Nested Loop (cost=0.00..108,597.10 rows=919 width=12) (actual time=1,046.913..1,055.285 rows=15 loops=1)

3. 154.180 154.180 ↑ 3.1 47,489 1

Index Scan Backward using replays_game_game_time on replays_game (cost=0.00..5,652.77 rows=147,119 width=12) (actual time=0.017..154.180 rows=47,489 loops=1)

4. 759.824 759.824 ↓ 0.0 0 47,489

Index Scan using replays_playeringame_game_id on replays_playeringame (cost=0.00..0.70 rows=1 width=4) (actual time=0.016..0.016 rows=0 loops=47,489)

  • Index Cond: (game_id = replays_game.id)
  • 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) AND (player_id = 60201))