explain.depesz.com

A tool for finding a real cause for slow queries.

Result: KX6

options
Did it help? Consider supporting us - Bitcoin address: 12v2hUztAk2LgzQ9H9LMwuU32urHMjZQnq
# exclusive inclusive rows x rows loops node
1. 0.262 462.719 ↓ 1.3 948 1

Limit (cost=4062.16..4069.21 rows=705 width=8) (actual time=462.193..462.719 rows=948 loops=1)

2. 0.709 462.457 ↓ 1.3 948 1

HashAggregate (cost=4062.16..4069.21 rows=705 width=8) (actual time=462.191..462.457 rows=948 loops=1)

3. 0.296 461.748 ↓ 1.3 948 1

Result (cost=6.33..4060.40 rows=705 width=8) (actual time=373.437..461.748 rows=948 loops=1)

4. 461.452 461.452 ↓ 1.3 948 1

Append (cost=6.33..4060.40 rows=705 width=8) (actual time=373.436..461.452 rows=948 loops=1)

  • -> Bitmap Heap Scan on events (cost=6.33..22.48 rows=2 width=8) (actual time=156.000..156.000 rows
  • Recheck Cond: (clock > 1335762000)
  • Filter: (source = 0)
  • -> Bitmap Index Scan on events_2 (cost=0.00..6.33 rows=410 width=0) (actual time=155.993..15
  • Index Cond: (clock > 1335762000)
  • -> Bitmap Heap Scan on events_y2012m04d28 events (cost=546.29..3992.97 rows=699 width=8) (actual t
  • Recheck Cond: (clock > 1335762000)
  • Filter: (source = 0)
  • -> Bitmap Index Scan on events_y2012m04d28_2 (cost=0.00..546.11 rows=34379 width=0) (actual
  • Index Cond: (clock > 1335762000)
  • -> Bitmap Heap Scan on events_y2012m05d05 events (cost=6.33..22.48 rows=2 width=8) (actual time=12
  • Recheck Cond: (clock > 1335762000)
  • Filter: (source = 0)
  • -> Bitmap Index Scan on events_y2012m05d05_2 (cost=0.00..6.33 rows=410 width=0) (actual time
  • Index Cond: (clock > 1335762000)
  • -> Bitmap Heap Scan on events_y2012m05d12 events (cost=6.33..22.48 rows=2 width=8) (actual time=65
  • Recheck Cond: (clock > 1335762000)
  • Filter: (source = 0)
  • -> Bitmap Index Scan on events_y2012m05d12_2 (cost=0.00..6.33 rows=410 width=0) (actual time
  • Index Cond: (clock > 1335762000)