Re: difficulties with time based queries - Mailing list pgsql-performance

From David Wilson
Subject Re: difficulties with time based queries
Date
Msg-id e7f9235d0904051646j7e8374afncf79e3708ae40c20@mail.gmail.com
Whole thread Raw
In response to difficulties with time based queries  ("Rainer Mager" <rainer@vanten.com>)
Responses Re: difficulties with time based queries
List pgsql-performance
On Sun, Apr 5, 2009 at 7:26 PM, Rainer Mager <rainer@vanten.com> wrote:
> Bitmap Heap Scan on ad_log  (cost=73372.57..3699152.24 rows=2488252
> width=32) (actual time=49792.862..64611.255 rows=2268490 loops=1)
>
>    Recheck Cond: ((date(start_time) < '2009-03-31'::date) AND
> (date(start_time) >= '2009-03-30'::date))
>
>    ->  Bitmap Index Scan on ad_log_date_all  (cost=0.00..72750.51
> rows=2488252 width=0) (actual time=49776.332..49776.332 rows=2268490
> loops=1)
>
>          Index Cond: ((date(start_time) < '2009-03-31'::date) AND
> (date(start_time) >= '2009-03-30'::date))
>
>  Total runtime: 65279.352 ms

The stats look good and it's using a viable index for your query. What
kind of hardware is this on, and what are the relevant postgresql.conf
lines? (Or, for that matter, what does iostat say while this query's
running?)

--
- David T. Wilson
david.t.wilson@gmail.com

pgsql-performance by date:

Previous
From: "Rainer Mager"
Date:
Subject: difficulties with time based queries
Next
From: PFC
Date:
Subject: Re: difficulties with time based queries