explain.depesz.com

PostgreSQL's explain analyze made readable

Result: xn1m

Settings
# exclusive inclusive rows x rows loops node
1. 0.012 30,517.469 ↑ 1.0 1 1

Limit (cost=5.32..24.92 rows=1 width=8) (actual time=30,517.458..30,517.469 rows=1 loops=1)

2. 21,604.083 30,517.457 ↑ 54,709.0 1 1

Hash Join (cost=5.32..1,072,498.21 rows=54,709 width=8) (actual time=30,517.456..30,517.457 rows=1 loops=1)

  • Hash Cond: (lower(twitter_followers.primary_screen_name) = (lower(twitter_usernames.name)))
3. 8,911.363 8,911.363 ↑ 1.0 46,557,901 1

Seq Scan on twitter_followers (cost=0.00..943,488.14 rows=46,667,114 width=18) (actual time=0.598..8,911.363 rows=46,557,901 loops=1)

4. 0.007 2.011 ↑ 1.0 1 1

Hash (cost=5.31..5.31 rows=1 width=32) (actual time=2.011..2.011 rows=1 loops=1)

  • Buckets: 1024 Batches: 1 Memory Usage: 9kB
5. 0.001 2.004 ↑ 1.0 1 1

Unique (cost=5.29..5.30 rows=1 width=32) (actual time=2.004..2.004 rows=1 loops=1)

6. 0.009 2.003 ↑ 1.0 1 1

Sort (cost=5.29..5.29 rows=1 width=32) (actual time=2.003..2.003 rows=1 loops=1)

  • Sort Key: (lower(twitter_usernames.name))
  • Sort Method: quicksort Memory: 25kB
7. 0.009 1.994 ↑ 1.0 1 1

Nested Loop (cost=0.84..5.28 rows=1 width=32) (actual time=1.992..1.994 rows=1 loops=1)

8. 1.605 1.605 ↑ 1.0 1 1

Index Only Scan using twitter_usernames_orgaizations_key2 on twitter_usernames_organizations (cost=0.42..2.64 rows=1 width=4) (actual time=1.604..1.605 rows=1 loops=1)

  • Index Cond: (organization_id = 1412228)
  • Heap Fetches: 1
9. 0.380 0.380 ↑ 1.0 1 1

Index Scan using twitter_usernames_pkey on twitter_usernames (cost=0.42..2.64 rows=1 width=16) (actual time=0.380..0.380 rows=1 loops=1)

  • Index Cond: (id = twitter_usernames_organizations.twitter_username_id)