Re: Query planner: current_* vs. explicit date

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, Chris Gamache <cgg007(at)yahoo(dot)com>
Cc: pgsql-sql <pgsql-sql(at)postgresql(dot)org>
Subject: Re: Query planner: current_* vs. explicit date
Date: 2003-10-22 20:25:18
Message-ID: 200310221325.18470.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

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

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Bruce Momjian 2003-10-22 20:37:02 Re: Expressional Indexes
Previous Message Josh Berkus 2003-10-22 20:22:26 Re: Expressional Indexes