| From: | Bill Moseley <moseley(at)hank(dot)org> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Question about a query plan |
| Date: | 2005-09-16 17:18:19 |
| Message-ID: | 20050916171819.GC17486@hank.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Sep 16, 2005 at 10:02:28AM -0500, Thomas O'Connell wrote:
>
> On Sep 16, 2005, at 9:18 AM, Bill Moseley wrote:
>
> >First question is why the planner is not using an index scan when I
> >use "now()" or CURRENT_TIMESTAMP?
>
> It also used to be the case (pre-8.0; I couldn't find in the release
> notes whether this was an 8.0 or 8.1 fix) that now() and
> CURRENT_TIMESTAMP were not indexable, I think because of mutability.
>
> For older versions of postgres, it's recommended that you determine
> the time in the client and use constant data in your query.
Interesting. I have a few VIEWs that include now(), but I guess I
could adjust and pass in the date from the client.
Thanks for the tip.
--
Bill Moseley
moseley(at)hank(dot)org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Emi Lu | 2005-09-16 17:44:21 | Neither column can be NULL if the column is part of the combination of primary key columns? |
| Previous Message | Bill Moseley | 2005-09-16 17:11:18 | Re: Question about a query plan |