Re: Index scan vs. Seq scan on timestamps - Mailing list pgsql-general

From Stephen Frost
Subject Re: Index scan vs. Seq scan on timestamps
Date
Msg-id 20041207024925.GN10437@ns.snowman.net
Whole thread Raw
In response to Re: Index scan vs. Seq scan on timestamps  (Stephan Szabo <sszabo@megazone.bigpanda.com>)
Responses Re: Index scan vs. Seq scan on timestamps  (Stephan Szabo <sszabo@megazone.bigpanda.com>)
List pgsql-general
* Stephan Szabo (sszabo@megazone.bigpanda.com) wrote:
> On Mon, 6 Dec 2004, Per Jensen wrote:
> > select count(*)
> > from accesslog
> > where time  between (timeofday()::timestamp - INTERVAL '30 d') and
> > timeofday()::timestamp;
>
> Besides the type issue, timeofday() is volatile and thus is not allowed to
> be turned into a constant in order to do an index scan because it's
> allowed to return different values for every row of the input.

Is there a way to say "just take the value of this function at the start
of the transaction and then have it be constant" in a query?

    Stephen

Attachment

pgsql-general by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: Index scan vs. Seq scan on timestamps
Next
From: Andrew - Supernews
Date:
Subject: Re: Index scan vs. Seq scan on timestamps