]> git.ipfire.org Git - thirdparty/postgresql.git/commit
Fix PlaceHolderVar mechanism's interaction with outer joins.
authorTom Lane <tgl@sss.pgh.pa.us>
Tue, 28 Sep 2010 18:15:42 +0000 (14:15 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Tue, 28 Sep 2010 18:15:42 +0000 (14:15 -0400)
commitdc9cc887b74bfa0d40829c4df66dead509fdd8f6
tree90e39f8b5f06e7acfd07bd7b1ba525f1af41643b
parent2dc2ea81f67b96473cefe8fc7d515bda37255660
Fix PlaceHolderVar mechanism's interaction with outer joins.

The point of a PlaceHolderVar is to allow a non-strict expression to be
evaluated below an outer join, after which its value bubbles up like a Var
and can be forced to NULL when the outer join's semantics require that.
However, there was a serious design oversight in that, namely that we
didn't ensure that there was actually a correct place in the plan tree
to evaluate the placeholder :-(.  It may be necessary to delay evaluation
of an outer join to ensure that a placeholder that should be evaluated
below the join can be evaluated there.  Per recent bug report from Kirill
Simonov.

Back-patch to 8.4 where the PlaceHolderVar mechanism was introduced.
src/backend/nodes/copyfuncs.c
src/backend/nodes/equalfuncs.c
src/backend/nodes/outfuncs.c
src/backend/optimizer/plan/initsplan.c
src/backend/optimizer/plan/planmain.c
src/backend/optimizer/util/placeholder.c
src/include/nodes/relation.h
src/include/optimizer/placeholder.h
src/test/regress/expected/join.out
src/test/regress/sql/join.sql