explain.depesz.com

A tool for finding a real cause for slow queries.

Result: PRke

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

Limit (cost=11,070.88..11,070.91 rows=15 width=12) (actual time=178.256..178.261 rows=15 loops=1)

2. 0.624 178.257 ↑ 109.3 15 1

Sort (cost=11,070.88..11,074.97 rows=1,639 width=12) (actual time=178.254..178.257 rows=15 loops=1)

  • Sort Key: replays_game.game_time
  • Sort Method: top-N heapsort Memory: 25kB
3. 71.312 177.633 ↓ 1.2 1,916 1

Hash Join (cost=5,983.81..11,030.66 rows=1,639 width=12) (actual time=104.932..177.633 rows=1,916 loops=1)

  • Hash Cond: (replays_playeringame.game_id = replays_game.id)
4. 1.830 1.830 ↓ 1.2 1,916 1

Index Scan using replays_playeringame_player_id on replays_playeringame (cost=0.00..4,285.18 rows=1,639 width=4) (actual time=0.013..1.830 rows=1,916 loops=1)

  • Index Cond: (player_id = 60201)
5. 53.502 104.491 ↑ 1.0 147,058 1

Hash (cost=3,426.58..3,426.58 rows=147,058 width=12) (actual time=104.491..104.491 rows=147,058 loops=1)

  • Buckets: 4096 Batches: 8 Memory Usage: 804kB
6. 50.989 50.989 ↑ 1.0 147,058 1

Seq Scan on replays_game (cost=0.00..3,426.58 rows=147,058 width=12) (actual time=0.020..50.989 rows=147,058 loops=1)