From: Josh Berkus <josh@agliodbs.com>
To: scott.marlowe <scott.marlowe@ihs.com>
To: Chris Gamache <cgg007@yahoo.com>
Cc: pgsql-sql <pgsql-sql@postgresql.org>
Subject: Re: Query planner: current_* vs. explicit date
Date: Wed, 22 Oct 2003 13:25:18 -0700
Message-ID: <200310221325.18470.josh@agliodbs.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0310221308070.12830-100000@css120.ihs.com>
References: <Pine.LNX.4.33.0310221308070.12830-100000@css120.ihs.com>
Scott, Chris,
> I'd guess that the planner doesn't know what current_date::timestamp is
> ahead of time, so it chooses a seq scan.
Yes, this is a known problem. There was a single-query workaround, but I
can't remember it right now.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: josh@agliodbs.com, scott.marlowe@ihs.com, cgg007@yahoo.com
Subject: Re: Query planner: current_* vs. explicit date
In-Reply-To: <200310221325.18470.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox