mirror of
https://github.com/postgres/postgres.git
synced 2025-06-13 07:41:39 +03:00
Make NestLoop plan nodes pass outer-relation variables into their inner
relation using the general PARAM_EXEC executor parameter mechanism, rather than the ad-hoc kluge of passing the outer tuple down through ExecReScan. The previous method was hard to understand and could never be extended to handle parameters coming from multiple join levels. This patch doesn't change the set of possible plans nor have any significant performance effect, but it's necessary infrastructure for future generalization of the concept of an inner indexscan plan. ExecReScan's second parameter is now unused, so it's removed.
This commit is contained in:
@ -8,7 +8,7 @@
|
||||
*
|
||||
*
|
||||
* IDENTIFICATION
|
||||
* $PostgreSQL: pgsql/src/backend/executor/nodeMergejoin.c,v 1.103 2010/07/06 19:18:56 momjian Exp $
|
||||
* $PostgreSQL: pgsql/src/backend/executor/nodeMergejoin.c,v 1.104 2010/07/12 17:01:05 tgl Exp $
|
||||
*
|
||||
*-------------------------------------------------------------------------
|
||||
*/
|
||||
@ -1680,7 +1680,7 @@ ExecEndMergeJoin(MergeJoinState *node)
|
||||
}
|
||||
|
||||
void
|
||||
ExecReScanMergeJoin(MergeJoinState *node, ExprContext *exprCtxt)
|
||||
ExecReScanMergeJoin(MergeJoinState *node)
|
||||
{
|
||||
ExecClearTuple(node->mj_MarkedTupleSlot);
|
||||
|
||||
@ -1695,9 +1695,9 @@ ExecReScanMergeJoin(MergeJoinState *node, ExprContext *exprCtxt)
|
||||
* if chgParam of subnodes is not null then plans will be re-scanned by
|
||||
* first ExecProcNode.
|
||||
*/
|
||||
if (((PlanState *) node)->lefttree->chgParam == NULL)
|
||||
ExecReScan(((PlanState *) node)->lefttree, exprCtxt);
|
||||
if (((PlanState *) node)->righttree->chgParam == NULL)
|
||||
ExecReScan(((PlanState *) node)->righttree, exprCtxt);
|
||||
if (node->js.ps.lefttree->chgParam == NULL)
|
||||
ExecReScan(node->js.ps.lefttree);
|
||||
if (node->js.ps.righttree->chgParam == NULL)
|
||||
ExecReScan(node->js.ps.righttree);
|
||||
|
||||
}
|
||||
|
Reference in New Issue
Block a user