7643bed58e
until Bind is received, so that actual parameter values are visible to the planner. Make use of the parameter values for estimation purposes (but don't fold them into the actual plan). This buys back most of the potential loss of plan quality that ensues from using out-of-line parameters instead of putting literal values right into the query text. This patch creates a notion of constant-folding expressions 'for estimation purposes only', in which case we can be more aggressive than the normal eval_const_expressions() logic can be. Right now the only difference in behavior is inserting bound values for Params, but it will be interesting to look at other possibilities. One that we've seen come up repeatedly is reducing now() and related functions to current values, so that queries like ... WHERE timestampcol > now() - '1 day' have some chance of being planned effectively. Oliver Jowett, with some kibitzing from Tom Lane. |
||
|---|---|---|
| .. | ||
| Makefile | ||
| allpaths.c | ||
| clausesel.c | ||
| costsize.c | ||
| indxpath.c | ||
| joinpath.c | ||
| joinrels.c | ||
| orindxpath.c | ||
| pathkeys.c | ||
| tidpath.c | ||