Postgres Pro
Downloads
Home   >   mailing lists

Re: Query tuning - Mailing list pgsql-performance

From Nikolas Everett
Subject Re: Query tuning
Date
Msg-id d4e11e980908191031q3871deadi2dbc3c6f70ffb688@mail.gmail.com
Whole thread Raw
In response to Re: Query tuning  (Grzegorz Jaśkiewicz <gryzman@gmail.com>)
Responses Re: Query tuning  (Kevin Kempter <kevink@consistentstate.com>)
List pgsql-performance
Tree view


2009/8/19 Grzegorz Jaśkiewicz <gryzman@gmail.com>
that seems to be the killer:

and time >= extract ('epoch' from timestamp '2009-08-12')
and time < extract ('epoch' from timestamp '2009-08-13' )

You probably need an index on time/epoch:

CREATE INDEX foo ON table(extract ('epoch' from timestamp time );

It looks like those extracts just make constant integer times. You probably just create an index on the time column.

Also, why not store times as timestamps?
 


or something like that, vacuum analyze and retry.

--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance

pgsql-performance by date:

Previous
From: Scott Carey
Date:
Subject: Re: Query tuning
Next
From: Kevin Kempter
Date:
Subject: Re: Query tuning