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