explain.depesz.com

A tool for finding a real cause for slow queries.

Result: vbC

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 0.047 4989.441 ↓ 2.0 2 1

Sort (cost=266427.32..266427.33 rows=1 width=812) (actual time=4989.440..4989.441 rows=2 loops=1)

  • Sort Key: hh.create_stamp
  • Sort Method: quicksort Memory: 25kB
2. 109.799 4989.394 ↓ 2.0 2 1

Hash Join (cost=5119.79..266427.31 rows=1 width=812) (actual time=110.848..4989.394 rows=2 loops=1)

  • Hash Cond: (fb_client.id = hh.related_client_id)
3. 4802.374 4879.470 ↓ 1.0 356699 1

Bitmap Heap Scan on fb_client (cost=5112.97..261561.10 rows=353410 width=28) (actual time=101.486..4879.470 rows=356699 loops=1)

  • Recheck Cond: (serverid = 'os114'::bpchar)
4. 77.096 77.096 ↓ 1.0 361669 1

Bitmap Index Scan on idx_public_fb_client_serverid (cost=0.00..5024.62 rows=353410 width=0) (actual time=77.096..77.096 rows=361669 loops=1)

  • Index Cond: (serverid = 'os114'::bpchar)
5. 0.006 0.125 ↓ 2.0 2 1

Hash (cost=6.80..6.80 rows=1 width=71) (actual time=0.125..0.125 rows=2 loops=1)

6. 0.119 0.119 ↓ 2.0 2 1

Index Scan using idx_client_relation_primary_client_id on fb_client_relation hh (cost=0.00..6.80 rows=1 width=71) (actual time=0.106..0.119 rows=2 loops=1)

  • Index Cond: (primary_client_id = 8819654)
  • Filter: ((serverid)::text = 'os114'::text)