explain.depesz.com

A tool for finding a real cause for slow queries.

Result: ITY

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

Aggregate (cost=1,038.53..1,038.54 rows=1 width=0) (actual time=56.900..56.901 rows=1 loops=1)

2.          

Initplan (forAggregate)

3. 0.018 0.018 ↑ 1.0 1 1

Index Scan using uk_account_acco_alias on account (cost=0.00..5.27 rows=1 width=4) (actual time=0.017..0.018 rows=1 loops=1)

  • Index Cond: ((acco_alias)::text = 'amilrj'::text)
4. 2.264 55.888 ↓ 37.4 1,646 1

Bitmap Heap Scan on message_sms_mo (cost=923.70..1,033.15 rows=44 width=0) (actual time=53.745..55.888 rows=1,646 loops=1)

  • Recheck Cond: ((acco_id = $0) AND (msmo_received >= '2012-04-01 00:00:00-03'::timestamp with time zone) AND (msmo_received < '2012-05-01 00:00:00-03'::timestamp with time zone))
  • Filter: ((msmo_mobile)::text !~~ '5500%'::text)
5. 2.409 53.624 ↓ 0.0 0 1

BitmapAnd (cost=923.70..923.70 rows=44 width=0) (actual time=53.624..53.624 rows=0 loops=1)

6. 2.847 2.847 ↓ 2.9 18,102 1

Bitmap Index Scan on message_sms_mo_by_account (cost=0.00..97.75 rows=6,261 width=0) (actual time=2.847..2.847 rows=18,102 loops=1)

  • Index Cond: (acco_id = $0)
7. 48.368 48.368 ↓ 7.5 360,750 1

Bitmap Index Scan on message_sms_mo_by_received (cost=0.00..825.67 rows=48,244 width=0) (actual time=48.368..48.368 rows=360,750 loops=1)

  • Index Cond: ((msmo_received >= '2012-04-01 00:00:00-03'::timestamp with time zone) AND (msmo_received < '2012-05-01 00:00:00-03'::timestamp with time zone))