explain.depesz.com

A tool for finding a real cause for slow queries.

Result: J69

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

Limit (cost=0.00..2,234.64 rows=15 width=12) (actual time=450.774..535.380 rows=15 loops=1)

2. 0.035 535.364 ↑ 48.6 15 1

Nested Loop (cost=0.00..108,603.73 rows=729 width=12) (actual time=450.772..535.364 rows=15 loops=1)

3. 33.797 535.299 ↑ 48.6 15 1

Nested Loop (cost=0.00..108,597.10 rows=729 width=16) (actual time=450.752..535.299 rows=15 loops=1)

4. 93.621 93.621 ↑ 6.1 23,993 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.014..93.621 rows=23,993 loops=1)

5. 407.881 407.881 ↓ 0.0 0 23,993

Index Scan using replays_playeringame_game_id on replays_playeringame (cost=0.00..0.70 rows=1 width=8) (actual time=0.017..0.017 rows=0 loops=23,993)

  • 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 = 58181))
6. 0.019 0.030 ↑ 1.0 1 15

Materialize (cost=0.00..4.07 rows=1 width=4) (actual time=0.002..0.002 rows=1 loops=15)

7. 0.011 0.011 ↑ 1.0 1 1

Index Scan using replays_player_pkey on replays_player (cost=0.00..4.07 rows=1 width=4) (actual time=0.010..0.011 rows=1 loops=1)

  • Index Cond: (id = 58181)