Home > mailing lists

Re: Query planner: current_* vs. explicit date - Mailing list pgsql-sql

From	Josh Berkus
Subject	Re: Query planner: current_* vs. explicit date
Date	October 22, 2003 20:28:05
Msg-id	200310221325.18470.josh@agliodbs.com Whole thread Raw
In response to	Re: Query planner: current_* vs. explicit date ("scott.marlowe" <scott.marlowe@ihs.com>)
Responses	Re: Query planner: current_* vs. explicit date (Tom Lane <tgl@sss.pgh.pa.us>)
List	pgsql-sql

Tree view

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 BerkusAglio Database SolutionsSan Francisco

pgsql-sql by date:

From: Josh Berkus
Date: 22 October 2003, 20:25:17
Subject: Re: Expressional Indexes

From: Bruce Momjian
Date: 22 October 2003, 20:37:43
Subject: Re: Expressional Indexes

Re: Query planner: current_* vs. explicit date - Mailing list pgsql-sql

Previous

Next