Re: Choice of bitmap scan over index scan - Mailing list pgsql-performance

From Jeremy Harris
Subject Re: Choice of bitmap scan over index scan
Date
Msg-id 4B49DE7F.8080808@wizmail.org
Whole thread Raw
In response to Choice of bitmap scan over index scan  (Mathieu De Zutter <mathieu@dezutter.org>)
Responses Re: Choice of bitmap scan over index scan
List pgsql-performance
On 01/10/2010 12:28 PM, Mathieu De Zutter wrote:
>Sort  (cost=481763.31..485634.61 rows=1548520 width=338) (actual time=5423.628..6286.148 rows=1551923 loops=1)
>   Sort Key: event_timestamp
  >  Sort Method:  external merge  Disk: 90488kB
>   ->  Seq Scan on log_event  (cost=0.00..79085.92 rows=1548520 width=338) (actual time=0.022..2195.527 rows=1551923
loops=1)
>         Filter: (event_timestamp > (now() - '1 year'::interval))
> Total runtime: 6407.377 ms

Needing to use an external (on-disk) sort method, when taking
only 90MB, looks odd.

- Jeremy

pgsql-performance by date:

Previous
From: Mathieu De Zutter
Date:
Subject: Choice of bitmap scan over index scan
Next
From: "Kevin Grittner"
Date:
Subject: Re: Choice of bitmap scan over index scan