Re: Speeding up index scans by truncating timestamp?

From: Michael Glaesemann <grzm(at)seespotcode(dot)net>
To: Derrick Rice <derrick(dot)rice(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Speeding up index scans by truncating timestamp?
Date: 2011-02-15 15:16:37
Message-ID: 91E7312C-44B9-4E33-9451-4BD2FB9C74EE@seespotcode.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Feb 15, 2011, at 10:00, Derrick Rice wrote:

>>
>> Would creating an index on the timestamp truncated to the *day* make the
>> index more efficient for queries which are interested in events falling in a
>> range of 7+ days?
>>
>
> I gave this a shot, changing the index to be on date_trunc('day',
> timestamp). PostgreSQL (8.2) then decided not to use the index at all. Not
> sure if this is a limitation of PostgreSQL or if it decided it was going to
> be more expensive than the alternative.
>
> Is the query optimizer capable of using the relationship between an index on
> date_trunc(foo) and a query with "where foo < bar and foo > baz" ? At this
> point the question is to satisfy my own curiosity.

Providing the table definition, queries, and EXPLAIN and EXPLAIN ANALYZE output would help people provide more specific feedback.

Michael Glaesemann
grzm seespotcode net

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Vick Khera 2011-02-15 15:20:12 Re: Speeding up index scans by truncating timestamp?
Previous Message Derrick Rice 2011-02-15 15:00:23 Re: Speeding up index scans by truncating timestamp?