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 1794484.567 ↑ 1.0 3 1

Limit (cost=50291.28..50291.28 rows=3 width=16) (actual time=1794484.566..1794484.567 rows=3 loops=1)

2. 0.065 1794484.563 ↑ 1.3 3 1

Sort (cost=50291.28..50291.29 rows=4 width=16) (actual time=1794484.562..1794484.563 rows=3 loops=1)

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

Bitmap Heap Scan on "YEAR" (cost=48569.54..50291.24 rows=4 width=16) (actual time=1794411.662..1794484.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 1794411.249 ↓ 0.0 0 1

BitmapAnd (cost=48569.54..48569.54 rows=430 width=0) (actual time=1794411.249..1794411.249 rows=0 loops=1)

5. 1793917.506 1793917.506 ↓ 7.8 1291933 1

Bitmap Index Scan on security_desc (cost=0.00..4722.94 rows=166029 width=0) (actual time=1793917.506..1793917.506 rows=1291933 loops=1)

  • Index Cond: ("SECURITY" = 'STW.AX'::bpchar)
6. 378.698 378.698 ↑ 1.0 2317130 1

Bitmap Index Scan on date_desc (cost=0.00..43846.35 rows=2368764 width=0) (actual time=378.698..378.698 rows=2317130 loops=1)

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