| From: | Thomas O'Connell <tfo(at)sitening(dot)com> |
|---|---|
| To: | Bill Moseley <moseley(at)hank(dot)org> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Question about a query plan |
| Date: | 2005-09-16 15:02:28 |
| Message-ID: | DF4319A7-9BE1-4B65-A010-599F1B45C1FF@sitening.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
Strategic Open Source: Open Your i™
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-469-5150
615-469-5151 (fax)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Ribe | 2005-09-16 16:58:56 | Re: Asychronous database replication |
| Previous Message | Peter Eisentraut | 2005-09-16 14:45:57 | Re: Question about a query plan |