mirror of
https://github.com/postgres/postgres.git
synced 2025-04-29 13:56:47 +03:00
useless substructure for its RangeTblEntry nodes. (I chose to keep using the same struct node type and just zero out the link fields for unneeded info, rather than making a separate ExecRangeTblEntry type --- it seemed too fragile to have two different rangetable representations.) Along the way, put subplans into a list in the toplevel PlannedStmt node, and have SubPlan nodes refer to them by list index instead of direct pointers. Vadim wanted to do that years ago, but I never understood what he was on about until now. It makes things a *whole* lot more robust, because we can stop worrying about duplicate processing of subplans during expression tree traversals. That's been a constant source of bugs, and it's finally gone. There are some consequent simplifications yet to be made, like not using a separate EState for subplans in the executor, but I'll tackle that later.
271 lines
7.4 KiB
C
271 lines
7.4 KiB
C
/*-------------------------------------------------------------------------
|
|
*
|
|
* nodeSubqueryscan.c
|
|
* Support routines for scanning subqueries (subselects in rangetable).
|
|
*
|
|
* This is just enough different from sublinks (nodeSubplan.c) to mean that
|
|
* we need two sets of code. Ought to look at trying to unify the cases.
|
|
*
|
|
*
|
|
* Portions Copyright (c) 1996-2007, PostgreSQL Global Development Group
|
|
* Portions Copyright (c) 1994, Regents of the University of California
|
|
*
|
|
*
|
|
* IDENTIFICATION
|
|
* $PostgreSQL: pgsql/src/backend/executor/nodeSubqueryscan.c,v 1.36 2007/02/22 22:00:23 tgl Exp $
|
|
*
|
|
*-------------------------------------------------------------------------
|
|
*/
|
|
/*
|
|
* INTERFACE ROUTINES
|
|
* ExecSubqueryScan scans a subquery.
|
|
* ExecSubqueryNext retrieve next tuple in sequential order.
|
|
* ExecInitSubqueryScan creates and initializes a subqueryscan node.
|
|
* ExecEndSubqueryScan releases any storage allocated.
|
|
* ExecSubqueryReScan rescans the relation
|
|
*
|
|
*/
|
|
#include "postgres.h"
|
|
|
|
#include "executor/execdebug.h"
|
|
#include "executor/nodeSubqueryscan.h"
|
|
|
|
static TupleTableSlot *SubqueryNext(SubqueryScanState *node);
|
|
|
|
/* ----------------------------------------------------------------
|
|
* Scan Support
|
|
* ----------------------------------------------------------------
|
|
*/
|
|
/* ----------------------------------------------------------------
|
|
* SubqueryNext
|
|
*
|
|
* This is a workhorse for ExecSubqueryScan
|
|
* ----------------------------------------------------------------
|
|
*/
|
|
static TupleTableSlot *
|
|
SubqueryNext(SubqueryScanState *node)
|
|
{
|
|
EState *estate;
|
|
ScanDirection direction;
|
|
TupleTableSlot *slot;
|
|
|
|
/*
|
|
* get information from the estate and scan state
|
|
*/
|
|
estate = node->ss.ps.state;
|
|
direction = estate->es_direction;
|
|
|
|
/*
|
|
* We need not support EvalPlanQual here, since we are not scanning a real
|
|
* relation.
|
|
*/
|
|
|
|
/*
|
|
* Get the next tuple from the sub-query.
|
|
*/
|
|
node->sss_SubEState->es_direction = direction;
|
|
|
|
slot = ExecProcNode(node->subplan);
|
|
|
|
/*
|
|
* We just overwrite our ScanTupleSlot with the subplan's result slot,
|
|
* rather than expending the cycles for ExecCopySlot().
|
|
*/
|
|
node->ss.ss_ScanTupleSlot = slot;
|
|
|
|
return slot;
|
|
}
|
|
|
|
/* ----------------------------------------------------------------
|
|
* ExecSubqueryScan(node)
|
|
*
|
|
* Scans the subquery sequentially and returns the next qualifying
|
|
* tuple.
|
|
* It calls the ExecScan() routine and passes it the access method
|
|
* which retrieve tuples sequentially.
|
|
*
|
|
*/
|
|
|
|
TupleTableSlot *
|
|
ExecSubqueryScan(SubqueryScanState *node)
|
|
{
|
|
/*
|
|
* use SubqueryNext as access method
|
|
*/
|
|
return ExecScan(&node->ss, (ExecScanAccessMtd) SubqueryNext);
|
|
}
|
|
|
|
/* ----------------------------------------------------------------
|
|
* ExecInitSubqueryScan
|
|
* ----------------------------------------------------------------
|
|
*/
|
|
SubqueryScanState *
|
|
ExecInitSubqueryScan(SubqueryScan *node, EState *estate, int eflags)
|
|
{
|
|
SubqueryScanState *subquerystate;
|
|
EState *sp_estate;
|
|
|
|
/* check for unsupported flags */
|
|
Assert(!(eflags & EXEC_FLAG_MARK));
|
|
|
|
/*
|
|
* SubqueryScan should not have any "normal" children. Also, if planner
|
|
* left anything in subrtable, it's fishy.
|
|
*/
|
|
Assert(outerPlan(node) == NULL);
|
|
Assert(innerPlan(node) == NULL);
|
|
Assert(node->subrtable == NIL);
|
|
|
|
/*
|
|
* create state structure
|
|
*/
|
|
subquerystate = makeNode(SubqueryScanState);
|
|
subquerystate->ss.ps.plan = (Plan *) node;
|
|
subquerystate->ss.ps.state = estate;
|
|
|
|
/*
|
|
* Miscellaneous initialization
|
|
*
|
|
* create expression context for node
|
|
*/
|
|
ExecAssignExprContext(estate, &subquerystate->ss.ps);
|
|
|
|
/*
|
|
* initialize child expressions
|
|
*/
|
|
subquerystate->ss.ps.targetlist = (List *)
|
|
ExecInitExpr((Expr *) node->scan.plan.targetlist,
|
|
(PlanState *) subquerystate);
|
|
subquerystate->ss.ps.qual = (List *)
|
|
ExecInitExpr((Expr *) node->scan.plan.qual,
|
|
(PlanState *) subquerystate);
|
|
|
|
#define SUBQUERYSCAN_NSLOTS 2
|
|
|
|
/*
|
|
* tuple table initialization
|
|
*/
|
|
ExecInitResultTupleSlot(estate, &subquerystate->ss.ps);
|
|
ExecInitScanTupleSlot(estate, &subquerystate->ss);
|
|
|
|
/*
|
|
* initialize subquery
|
|
*
|
|
* This should agree with ExecInitSubPlan
|
|
*
|
|
* The subquery needs its own EState because it has its own rangetable. It
|
|
* shares our Param ID space and es_query_cxt, however. XXX if rangetable
|
|
* access were done differently, the subquery could share our EState,
|
|
* which would eliminate some thrashing about in this module...
|
|
*
|
|
* XXX make that happen!
|
|
*/
|
|
sp_estate = CreateSubExecutorState(estate);
|
|
subquerystate->sss_SubEState = sp_estate;
|
|
|
|
sp_estate->es_range_table = estate->es_range_table;
|
|
sp_estate->es_param_list_info = estate->es_param_list_info;
|
|
sp_estate->es_param_exec_vals = estate->es_param_exec_vals;
|
|
sp_estate->es_tupleTable =
|
|
ExecCreateTupleTable(ExecCountSlotsNode(node->subplan) + 10);
|
|
sp_estate->es_snapshot = estate->es_snapshot;
|
|
sp_estate->es_crosscheck_snapshot = estate->es_crosscheck_snapshot;
|
|
sp_estate->es_instrument = estate->es_instrument;
|
|
sp_estate->es_plannedstmt = estate->es_plannedstmt;
|
|
|
|
/*
|
|
* Start up the subplan (this is a very cut-down form of InitPlan())
|
|
*/
|
|
subquerystate->subplan = ExecInitNode(node->subplan, sp_estate, eflags);
|
|
|
|
subquerystate->ss.ps.ps_TupFromTlist = false;
|
|
|
|
/*
|
|
* Initialize scan tuple type (needed by ExecAssignScanProjectionInfo).
|
|
* Because the subplan is in its own memory context, we need to copy its
|
|
* result tuple type not just link to it; else the tupdesc will disappear
|
|
* too soon during shutdown.
|
|
*/
|
|
ExecAssignScanType(&subquerystate->ss,
|
|
CreateTupleDescCopy(ExecGetResultType(subquerystate->subplan)));
|
|
|
|
/*
|
|
* Initialize result tuple type and projection info.
|
|
*/
|
|
ExecAssignResultTypeFromTL(&subquerystate->ss.ps);
|
|
ExecAssignScanProjectionInfo(&subquerystate->ss);
|
|
|
|
return subquerystate;
|
|
}
|
|
|
|
int
|
|
ExecCountSlotsSubqueryScan(SubqueryScan *node)
|
|
{
|
|
/*
|
|
* The subplan has its own tuple table and must not be counted here!
|
|
*/
|
|
return ExecCountSlotsNode(outerPlan(node)) +
|
|
ExecCountSlotsNode(innerPlan(node)) +
|
|
SUBQUERYSCAN_NSLOTS;
|
|
}
|
|
|
|
/* ----------------------------------------------------------------
|
|
* ExecEndSubqueryScan
|
|
*
|
|
* frees any storage allocated through C routines.
|
|
* ----------------------------------------------------------------
|
|
*/
|
|
void
|
|
ExecEndSubqueryScan(SubqueryScanState *node)
|
|
{
|
|
/*
|
|
* Free the exprcontext
|
|
*/
|
|
ExecFreeExprContext(&node->ss.ps);
|
|
|
|
/*
|
|
* clean out the upper tuple table
|
|
*/
|
|
ExecClearTuple(node->ss.ps.ps_ResultTupleSlot);
|
|
node->ss.ss_ScanTupleSlot = NULL; /* not ours to clear */
|
|
|
|
/*
|
|
* close down subquery
|
|
*/
|
|
ExecEndPlan(node->subplan, node->sss_SubEState);
|
|
|
|
FreeExecutorState(node->sss_SubEState);
|
|
}
|
|
|
|
/* ----------------------------------------------------------------
|
|
* ExecSubqueryReScan
|
|
*
|
|
* Rescans the relation.
|
|
* ----------------------------------------------------------------
|
|
*/
|
|
void
|
|
ExecSubqueryReScan(SubqueryScanState *node, ExprContext *exprCtxt)
|
|
{
|
|
EState *estate;
|
|
|
|
estate = node->ss.ps.state;
|
|
|
|
/*
|
|
* ExecReScan doesn't know about my subplan, so I have to do
|
|
* changed-parameter signaling myself. This is just as well, because the
|
|
* subplan has its own memory context in which its chgParam state lives.
|
|
*/
|
|
if (node->ss.ps.chgParam != NULL)
|
|
UpdateChangedParamSet(node->subplan, node->ss.ps.chgParam);
|
|
|
|
/*
|
|
* if chgParam of subnode is not null then plan will be re-scanned by
|
|
* first ExecProcNode.
|
|
*/
|
|
if (node->subplan->chgParam == NULL)
|
|
ExecReScan(node->subplan, NULL);
|
|
|
|
node->ss.ss_ScanTupleSlot = NULL;
|
|
node->ss.ps.ps_TupFromTlist = false;
|
|
}
|