explain.depesz.com

PostgreSQL's explain analyze made readable

Result: 3i88

Settings

Optimization(s) for this plan:

# exclusive inclusive rows x rows loops node
1. 109.406 2,751.431 ↓ 2.1 500,000 1

Unique (cost=139,521.03..142,441.68 rows=233,652 width=45) (actual time=2,478.074..2,751.431 rows=500,000 loops=1)

2.          

Initplan (forUnique)

3. 0.000 0.000 ↑ 1.0 1 1

Result (cost=0.00..0.01 rows=1 width=0) (actual time=0.000..0.000 rows=1 loops=1)

4. 744.118 2,642.025 ↓ 2.1 500,000 1

Sort (cost=139,521.02..140,105.15 rows=233,652 width=45) (actual time=2,478.072..2,642.025 rows=500,000 loops=1)

  • Sort Key: player_personal_details.player_id, player_personal_details.player_first_name, player_personal_details.player_last_name, player_personal_details.player_username
  • Sort Method: external merge Disk: 28008kB
5. 53.579 1,897.907 ↓ 2.1 500,000 1

Result (cost=42,445.75..111,497.27 rows=233,652 width=45) (actual time=688.264..1,897.907 rows=500,000 loops=1)

  • One-Time Filter: $0
6. 760.899 1,844.328 ↓ 2.1 500,000 1

Hash Join (cost=42,445.75..111,497.27 rows=233,652 width=45) (actual time=688.261..1,844.328 rows=500,000 loops=1)

  • Hash Cond: (player_personal_details.player_id = player_back_office_data.player_id)
7. 395.630 395.630 ↑ 1.0 500,000 1

Seq Scan on player_personal_details (cost=0.00..51,387.00 rows=500,000 width=45) (actual time=0.003..395.630 rows=500,000 loops=1)

8. 129.978 687.799 ↓ 2.1 500,000 1

Hash (cost=38,612.10..38,612.10 rows=233,652 width=8) (actual time=687.799..687.799 rows=500,000 loops=1)

  • Buckets: 16384 Batches: 4 (originally 2) Memory Usage: 4097kB
9. 557.821 557.821 ↓ 2.1 500,000 1

Seq Scan on player_back_office_data (cost=0.00..38,612.10 rows=233,652 width=8) (actual time=0.046..557.821 rows=500,000 loops=1)

  • Filter: (SubPlan 2)
10.          

SubPlan (forSeq Scan)

11. 0.000 0.000 ↑ 1.0 1 500,000

Result (cost=0.00..0.01 rows=1 width=0) (actual time=0.000..0.000 rows=1 loops=500,000)