From d04db370720ece56ffcad54e46cf03483c742ebb Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Fri, 9 Jan 2009 15:46:11 +0000 Subject: Arrange for function default arguments to be processed properly in expressions that are set up for execution with ExecPrepareExpr rather than going through the full planner process. By introducing an explicit notion of "expression planning", this patch also lays a bit of groundwork for maybe someday allowing sub-selects in standalone expressions. --- src/backend/executor/README | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'src/backend/executor/README') diff --git a/src/backend/executor/README b/src/backend/executor/README index 7644cc2cc42..467d6272d1e 100644 --- a/src/backend/executor/README +++ b/src/backend/executor/README @@ -1,4 +1,4 @@ -$PostgreSQL: pgsql/src/backend/executor/README,v 1.7 2008/03/21 13:23:28 momjian Exp $ +$PostgreSQL: pgsql/src/backend/executor/README,v 1.8 2009/01/09 15:46:10 tgl Exp $ The Postgres Executor ===================== @@ -124,7 +124,8 @@ be hidden inside function calls). This case has a flow of control like creates per-tuple context ExecPrepareExpr - switch to per-query context to run ExecInitExpr + temporarily switch to per-query context + run the expression through expression_planner ExecInitExpr Repeatedly do: -- cgit v1.2.3