explain.depesz.com

A tool for finding a real cause for slow queries.

Result: VqC

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 0.004 1,794,484.567 ↑ 1.0 3 1

Limit (cost=50,291.28..50,291.28 rows=3 width=16) (actual time=1,794,484.566..1,794,484.567 rows=3 loops=1)

2. 0.065 1,794,484.563 ↑ 1.3 3 1

Sort (cost=50,291.28..50,291.29 rows=4 width=16) (actual time=1,794,484.562..1,794,484.563 rows=3 loops=1)

  • Sort Key: "TIME
  • Sort Method: top-N heapsort Memory: 25kB
3. 73.249 1,794,484.498 ↓ 5.0 20 1

Bitmap Heap Scan on "YEAR" (cost=48,569.54..50,291.24 rows=4 width=16) (actual time=1,794,411.662..1,794,484.498 rows=20 loops=1)

  • Recheck Cond: (("SECURITY" = 'STW.AX'::bpchar) AND ("DATE" = '2010-03-01'::date))
  • Filter: (("TIME" < '10:16:00'::time without time zone) AND ("TYPE" = 'TRADE'::bpchar))
4. 115.045 1,794,411.249 ↓ 0.0 0 1

BitmapAnd (cost=48,569.54..48,569.54 rows=430 width=0) (actual time=1,794,411.249..1,794,411.249 rows=0 loops=1)

5. 1,793,917.506 1,793,917.506 ↓ 7.8 1,291,933 1

Bitmap Index Scan on security_desc (cost=0.00..4,722.94 rows=166,029 width=0) (actual time=1,793,917.506..1,793,917.506 rows=1,291,933 loops=1)

  • Index Cond: ("SECURITY" = 'STW.AX'::bpchar)
6. 378.698 378.698 ↑ 1.0 2,317,130 1

Bitmap Index Scan on date_desc (cost=0.00..43,846.35 rows=2,368,764 width=0) (actual time=378.698..378.698 rows=2,317,130 loops=1)

  • Index Cond: ("DATE" = '2010-03-01'::date)