Log Message: ----------- Put function expressions and values lists into FunctionScan and ValuesScan plan nodes, so that the executor does not need to get these items from the range table at runtime. This will avoid needing to include these fields in the compact range table I'm expecting to make the executor use.
Modified Files:
--------------
pgsql/src/backend/commands:
explain.c (r1.154 -> r1.155)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/explain.c.diff?r1=1.154&r2=1.155)
pgsql/src/backend/executor:
execAmi.c (r1.91 -> r1.92)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/execAmi.c.diff?r1=1.91&r2=1.92)
nodeFunctionscan.c (r1.42 -> r1.43)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeFunctionscan.c.diff?r1=1.42&r2=1.43)
nodeValuesscan.c (r1.5 -> r1.6)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeValuesscan.c.diff?r1=1.5&r2=1.6)
pgsql/src/backend/nodes:
copyfuncs.c (r1.365 -> r1.366)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/copyfuncs.c.diff?r1=1.365&r2=1.366)
outfuncs.c (r1.297 -> r1.298)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/outfuncs.c.diff?r1=1.297&r2=1.298)
pgsql/src/backend/optimizer/plan:
createplan.c (r1.224 -> r1.225)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/createplan.c.diff?r1=1.224&r2=1.225)
setrefs.c (r1.129 -> r1.130)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/setrefs.c.diff?r1=1.129&r2=1.130)
subselect.c (r1.118 -> r1.119)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/subselect.c.diff?r1=1.118&r2=1.119)
pgsql/src/include/nodes:
plannodes.h (r1.89 -> r1.90)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/plannodes.h.diff?r1=1.89&r2=1.90)
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
