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) ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
