explain.depesz.com

A tool for finding a real cause for slow queries.

Result: npC

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 778.538 42725.409 ↓ 1.0 387451 1

Sort (cost=1525453.05..1526404.89 rows=380737 width=38) (actual time=42473.084..42725.409 rows=387451 loops=1)

  • Sort Key: public.sms_all.session, (abs(public.sms_all.user_id))
  • Sort Method: quicksort Memory: 42558kB
2. 25331.432 41946.871 ↓ 1.0 387451 1

Hash Join (cost=591621.60..1490161.70 rows=380737 width=38) (actual time=11982.614..41946.871 rows=387451 loops=1)

  • Hash Cond: (public.sms_all.session = public.sms_all.session)
3. 15386.024 15386.024 ↑ 1.0 21043299 1

Seq Scan on sms_all (cost=0.00..788433.26 rows=21069526 width=38) (actual time=0.036..15386.024 rows=21043299 loops=1)

4. 29.424 1229.415 ↓ 24.1 41215 1

Hash (cost=591600.20..591600.20 rows=1712 width=8) (actual time=1229.415..1229.415 rows=41215 loops=1)

5. 238.864 1199.991 ↓ 24.1 41215 1

Unique (cost=589679.69..591583.08 rows=1712 width=8) (actual time=746.505..1199.991 rows=41215 loops=1)

6. 605.350 961.127 ↑ 1.1 360417 1

Sort (cost=589679.69..590631.39 rows=380678 width=8) (actual time=746.501..961.127 rows=360417 loops=1)

  • Sort Key: public.sms_all.session
  • Sort Method: quicksort Memory: 29183kB
7. 312.194 355.777 ↑ 1.1 360417 1

Bitmap Heap Scan on sms_all (cost=8076.51..554394.25 rows=380678 width=8) (actual time=45.527..355.777 rows=360417 loops=1)

  • Recheck Cond: ((send_date >= '2012-04-17 00:00:00+02'::timestamp with time zone) AND (send_date <= '2012-05-17 00:00:00+02'::timestamp with time zone))
8. 43.583 43.583 ↑ 1.1 360417 1

Bitmap Index Scan on sms_all_send_date (cost=0.00..7981.34 rows=380678 width=0) (actual time=43.583..43.583 rows=360417 loops=1)

  • Index Cond: ((send_date >= '2012-04-17 00:00:00+02'::timestamp with time zone) AND (send_date <= '2012-05-17 00:00:00+02'::timestamp with time zone))