|
|
|
|
/*-------------------------------------------------------------------------
|
|
|
|
|
*
|
|
|
|
|
* execProcnode.c
|
|
|
|
|
* contains dispatch functions which call the appropriate "initialize",
|
|
|
|
|
* "get a tuple", and "cleanup" routines for the given node type.
|
|
|
|
|
* If the node has children, then it will presumably call ExecInitNode,
|
|
|
|
|
* ExecProcNode, or ExecEndNode on its subnodes and do the appropriate
|
|
|
|
|
* processing.
|
|
|
|
|
*
|
|
|
|
|
* Portions Copyright (c) 1996-2017, PostgreSQL Global Development Group
|
|
|
|
|
* Portions Copyright (c) 1994, Regents of the University of California
|
|
|
|
|
*
|
|
|
|
|
*
|
|
|
|
|
* IDENTIFICATION
|
|
|
|
|
* src/backend/executor/execProcnode.c
|
|
|
|
|
*
|
|
|
|
|
*-------------------------------------------------------------------------
|
|
|
|
|
*/
|
|
|
|
|
/*
|
|
|
|
|
* INTERFACE ROUTINES
|
|
|
|
|
* ExecInitNode - initialize a plan node and its subplans
|
|
|
|
|
* ExecProcNode - get a tuple by executing the plan node
|
|
|
|
|
* ExecEndNode - shut down a plan node and its subplans
|
|
|
|
|
*
|
|
|
|
|
* NOTES
|
|
|
|
|
* This used to be three files. It is now all combined into
|
|
|
|
|
* one file so that it is easier to keep ExecInitNode, ExecProcNode,
|
|
|
|
|
* and ExecEndNode in sync when new nodes are added.
|
|
|
|
|
*
|
|
|
|
|
* EXAMPLE
|
|
|
|
|
* Suppose we want the age of the manager of the shoe department and
|
|
|
|
|
* the number of employees in that department. So we have the query:
|
|
|
|
|
*
|
|
|
|
|
* select DEPT.no_emps, EMP.age
|
|
|
|
|
* from DEPT, EMP
|
|
|
|
|
* where EMP.name = DEPT.mgr and
|
|
|
|
|
* DEPT.name = "shoe"
|
|
|
|
|
*
|
|
|
|
|
* Suppose the planner gives us the following plan:
|
|
|
|
|
*
|
|
|
|
|
* Nest Loop (DEPT.mgr = EMP.name)
|
|
|
|
|
* / \
|
|
|
|
|
* / \
|
|
|
|
|
* Seq Scan Seq Scan
|
|
|
|
|
* DEPT EMP
|
|
|
|
|
* (name = "shoe")
|
|
|
|
|
*
|
|
|
|
|
* ExecutorStart() is called first.
|
|
|
|
|
* It calls InitPlan() which calls ExecInitNode() on
|
|
|
|
|
* the root of the plan -- the nest loop node.
|
|
|
|
|
*
|
|
|
|
|
* * ExecInitNode() notices that it is looking at a nest loop and
|
|
|
|
|
* as the code below demonstrates, it calls ExecInitNestLoop().
|
|
|
|
|
* Eventually this calls ExecInitNode() on the right and left subplans
|
|
|
|
|
* and so forth until the entire plan is initialized. The result
|
|
|
|
|
* of ExecInitNode() is a plan state tree built with the same structure
|
|
|
|
|
* as the underlying plan tree.
|
|
|
|
|
*
|
|
|
|
|
* * Then when ExecutorRun() is called, it calls ExecutePlan() which calls
|
|
|
|
|
* ExecProcNode() repeatedly on the top node of the plan state tree.
|
|
|
|
|
* Each time this happens, ExecProcNode() will end up calling
|
|
|
|
|
* ExecNestLoop(), which calls ExecProcNode() on its subplans.
|
|
|
|
|
* Each of these subplans is a sequential scan so ExecSeqScan() is
|
|
|
|
|
* called. The slots returned by ExecSeqScan() may contain
|
|
|
|
|
* tuples which contain the attributes ExecNestLoop() uses to
|
|
|
|
|
* form the tuples it returns.
|
|
|
|
|
*
|
|
|
|
|
* * Eventually ExecSeqScan() stops returning tuples and the nest
|
|
|
|
|
* loop join ends. Lastly, ExecutorEnd() calls ExecEndNode() which
|
|
|
|
|
* calls ExecEndNestLoop() which in turn calls ExecEndNode() on
|
|
|
|
|
* its subplans which result in ExecEndSeqScan().
|
|
|
|
|
*
|
|
|
|
|
* This should show how the executor works by having
|
|
|
|
|
* ExecInitNode(), ExecProcNode() and ExecEndNode() dispatch
|
|
|
|
|
* their work to the appropriate node support routines which may
|
|
|
|
|
* in turn call these routines themselves on their subplans.
|
|
|
|
|
*/
|
|
|
|
|
#include "postgres.h"
|
|
|
|
|
|
|
|
|
|
#include "executor/executor.h"
|
|
|
|
|
#include "executor/nodeAgg.h"
|
|
|
|
|
#include "executor/nodeAppend.h"
|
|
|
|
|
#include "executor/nodeBitmapAnd.h"
|
|
|
|
|
#include "executor/nodeBitmapHeapscan.h"
|
|
|
|
|
#include "executor/nodeBitmapIndexscan.h"
|
|
|
|
|
#include "executor/nodeBitmapOr.h"
|
|
|
|
|
#include "executor/nodeCtescan.h"
|
|
|
|
|
#include "executor/nodeCustom.h"
|
|
|
|
|
#include "executor/nodeForeignscan.h"
|
|
|
|
|
#include "executor/nodeFunctionscan.h"
|
Move targetlist SRF handling from expression evaluation to new executor node.
Evaluation of set returning functions (SRFs_ in the targetlist (like SELECT
generate_series(1,5)) so far was done in the expression evaluation (i.e.
ExecEvalExpr()) and projection (i.e. ExecProject/ExecTargetList) code.
This meant that most executor nodes performing projection, and most
expression evaluation functions, had to deal with the possibility that an
evaluated expression could return a set of return values.
That's bad because it leads to repeated code in a lot of places. It also,
and that's my (Andres's) motivation, made it a lot harder to implement a
more efficient way of doing expression evaluation.
To fix this, introduce a new executor node (ProjectSet) that can evaluate
targetlists containing one or more SRFs. To avoid the complexity of the old
way of handling nested expressions returning sets (e.g. having to pass up
ExprDoneCond, and dealing with arguments to functions returning sets etc.),
those SRFs can only be at the top level of the node's targetlist. The
planner makes sure (via split_pathtarget_at_srfs()) that SRF evaluation is
only necessary in ProjectSet nodes and that SRFs are only present at the
top level of the node's targetlist. If there are nested SRFs the planner
creates multiple stacked ProjectSet nodes. The ProjectSet nodes always get
input from an underlying node.
We also discussed and prototyped evaluating targetlist SRFs using ROWS
FROM(), but that turned out to be more complicated than we'd hoped.
While moving SRF evaluation to ProjectSet would allow to retain the old
"least common multiple" behavior when multiple SRFs are present in one
targetlist (i.e. continue returning rows until all SRFs are at the end of
their input at the same time), we decided to instead only return rows till
all SRFs are exhausted, returning NULL for already exhausted ones. We
deemed the previous behavior to be too confusing, unexpected and actually
not particularly useful.
As a side effect, the previously prohibited case of multiple set returning
arguments to a function, is now allowed. Not because it's particularly
desirable, but because it ends up working and there seems to be no argument
for adding code to prohibit it.
Currently the behavior for COALESCE and CASE containing SRFs has changed,
returning multiple rows from the expression, even when the SRF containing
"arm" of the expression is not evaluated. That's because the SRFs are
evaluated in a separate ProjectSet node. As that's quite confusing, we're
likely to instead prohibit SRFs in those places. But that's still being
discussed, and the code would reside in places not touched here, so that's
a task for later.
There's a lot of, now superfluous, code dealing with set return expressions
around. But as the changes to get rid of those are verbose largely boring,
it seems better for readability to keep the cleanup as a separate commit.
Author: Tom Lane and Andres Freund
Discussion: https://postgr.es/m/20160822214023.aaxz5l4igypowyri@alap3.anarazel.de
9 years ago
|
|
|
#include "executor/nodeGather.h"
|
|
|
|
|
#include "executor/nodeGroup.h"
|
|
|
|
|
#include "executor/nodeHash.h"
|
|
|
|
|
#include "executor/nodeHashjoin.h"
|
|
|
|
|
#include "executor/nodeIndexonlyscan.h"
|
|
|
|
|
#include "executor/nodeIndexscan.h"
|
|
|
|
|
#include "executor/nodeLimit.h"
|
|
|
|
|
#include "executor/nodeLockRows.h"
|
|
|
|
|
#include "executor/nodeMaterial.h"
|
|
|
|
|
#include "executor/nodeMergeAppend.h"
|
|
|
|
|
#include "executor/nodeMergejoin.h"
|
|
|
|
|
#include "executor/nodeModifyTable.h"
|
|
|
|
|
#include "executor/nodeNestloop.h"
|
Move targetlist SRF handling from expression evaluation to new executor node.
Evaluation of set returning functions (SRFs_ in the targetlist (like SELECT
generate_series(1,5)) so far was done in the expression evaluation (i.e.
ExecEvalExpr()) and projection (i.e. ExecProject/ExecTargetList) code.
This meant that most executor nodes performing projection, and most
expression evaluation functions, had to deal with the possibility that an
evaluated expression could return a set of return values.
That's bad because it leads to repeated code in a lot of places. It also,
and that's my (Andres's) motivation, made it a lot harder to implement a
more efficient way of doing expression evaluation.
To fix this, introduce a new executor node (ProjectSet) that can evaluate
targetlists containing one or more SRFs. To avoid the complexity of the old
way of handling nested expressions returning sets (e.g. having to pass up
ExprDoneCond, and dealing with arguments to functions returning sets etc.),
those SRFs can only be at the top level of the node's targetlist. The
planner makes sure (via split_pathtarget_at_srfs()) that SRF evaluation is
only necessary in ProjectSet nodes and that SRFs are only present at the
top level of the node's targetlist. If there are nested SRFs the planner
creates multiple stacked ProjectSet nodes. The ProjectSet nodes always get
input from an underlying node.
We also discussed and prototyped evaluating targetlist SRFs using ROWS
FROM(), but that turned out to be more complicated than we'd hoped.
While moving SRF evaluation to ProjectSet would allow to retain the old
"least common multiple" behavior when multiple SRFs are present in one
targetlist (i.e. continue returning rows until all SRFs are at the end of
their input at the same time), we decided to instead only return rows till
all SRFs are exhausted, returning NULL for already exhausted ones. We
deemed the previous behavior to be too confusing, unexpected and actually
not particularly useful.
As a side effect, the previously prohibited case of multiple set returning
arguments to a function, is now allowed. Not because it's particularly
desirable, but because it ends up working and there seems to be no argument
for adding code to prohibit it.
Currently the behavior for COALESCE and CASE containing SRFs has changed,
returning multiple rows from the expression, even when the SRF containing
"arm" of the expression is not evaluated. That's because the SRFs are
evaluated in a separate ProjectSet node. As that's quite confusing, we're
likely to instead prohibit SRFs in those places. But that's still being
discussed, and the code would reside in places not touched here, so that's
a task for later.
There's a lot of, now superfluous, code dealing with set return expressions
around. But as the changes to get rid of those are verbose largely boring,
it seems better for readability to keep the cleanup as a separate commit.
Author: Tom Lane and Andres Freund
Discussion: https://postgr.es/m/20160822214023.aaxz5l4igypowyri@alap3.anarazel.de
9 years ago
|
|
|
#include "executor/nodeProjectSet.h"
|
|
|
|
|
#include "executor/nodeRecursiveunion.h"
|
|
|
|
|
#include "executor/nodeResult.h"
|
|
|
|
|
#include "executor/nodeSamplescan.h"
|
|
|
|
|
#include "executor/nodeSeqscan.h"
|
|
|
|
|
#include "executor/nodeSetOp.h"
|
|
|
|
|
#include "executor/nodeSort.h"
|
|
|
|
|
#include "executor/nodeSubplan.h"
|
|
|
|
|
#include "executor/nodeSubqueryscan.h"
|
|
|
|
|
#include "executor/nodeTableFuncscan.h"
|
|
|
|
|
#include "executor/nodeTidscan.h"
|
|
|
|
|
#include "executor/nodeUnique.h"
|
|
|
|
|
#include "executor/nodeValuesscan.h"
|
|
|
|
|
#include "executor/nodeWindowAgg.h"
|
|
|
|
|
#include "executor/nodeWorktablescan.h"
|
Add a Gather executor node.
A Gather executor node runs any number of copies of a plan in an equal
number of workers and merges all of the results into a single tuple
stream. It can also run the plan itself, if the workers are
unavailable or haven't started up yet. It is intended to work with
the Partial Seq Scan node which will be added in future commits.
It could also be used to implement parallel query of a different sort
by itself, without help from Partial Seq Scan, if the single_copy mode
is used. In that mode, a worker executes the plan, and the parallel
leader does not, merely collecting the worker's results. So, a Gather
node could be inserted into a plan to split the execution of that plan
across two processes. Nested Gather nodes aren't currently supported,
but we might want to add support for that in the future.
There's nothing in the planner to actually generate Gather nodes yet,
so it's not quite time to break out the champagne. But we're getting
close.
Amit Kapila. Some designs suggestions were provided by me, and I also
reviewed the patch. Single-copy mode, documentation, and other minor
changes also by me.
10 years ago
|
|
|
#include "nodes/nodeFuncs.h"
|
|
|
|
|
#include "miscadmin.h"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/* ------------------------------------------------------------------------
|
|
|
|
|
* ExecInitNode
|
|
|
|
|
*
|
|
|
|
|
* Recursively initializes all the nodes in the plan tree rooted
|
|
|
|
|
* at 'node'.
|
|
|
|
|
*
|
|
|
|
|
* Inputs:
|
|
|
|
|
* 'node' is the current node of the plan produced by the query planner
|
|
|
|
|
* 'estate' is the shared execution state for the plan tree
|
|
|
|
|
* 'eflags' is a bitwise OR of flag bits described in executor.h
|
|
|
|
|
*
|
|
|
|
|
* Returns a PlanState node corresponding to the given Plan node.
|
|
|
|
|
* ------------------------------------------------------------------------
|
|
|
|
|
*/
|
|
|
|
|
PlanState *
|
|
|
|
|
ExecInitNode(Plan *node, EState *estate, int eflags)
|
|
|
|
|
{
|
|
|
|
|
PlanState *result;
|
|
|
|
|
List *subps;
|
|
|
|
|
ListCell *l;
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* do nothing when we get to the end of a leaf on tree.
|
|
|
|
|
*/
|
|
|
|
|
if (node == NULL)
|
|
|
|
|
return NULL;
|
|
|
|
|
|
|
|
|
|
switch (nodeTag(node))
|
|
|
|
|
{
|
|
|
|
|
/*
|
|
|
|
|
* control nodes
|
|
|
|
|
*/
|
|
|
|
|
case T_Result:
|
|
|
|
|
result = (PlanState *) ExecInitResult((Result *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
Move targetlist SRF handling from expression evaluation to new executor node.
Evaluation of set returning functions (SRFs_ in the targetlist (like SELECT
generate_series(1,5)) so far was done in the expression evaluation (i.e.
ExecEvalExpr()) and projection (i.e. ExecProject/ExecTargetList) code.
This meant that most executor nodes performing projection, and most
expression evaluation functions, had to deal with the possibility that an
evaluated expression could return a set of return values.
That's bad because it leads to repeated code in a lot of places. It also,
and that's my (Andres's) motivation, made it a lot harder to implement a
more efficient way of doing expression evaluation.
To fix this, introduce a new executor node (ProjectSet) that can evaluate
targetlists containing one or more SRFs. To avoid the complexity of the old
way of handling nested expressions returning sets (e.g. having to pass up
ExprDoneCond, and dealing with arguments to functions returning sets etc.),
those SRFs can only be at the top level of the node's targetlist. The
planner makes sure (via split_pathtarget_at_srfs()) that SRF evaluation is
only necessary in ProjectSet nodes and that SRFs are only present at the
top level of the node's targetlist. If there are nested SRFs the planner
creates multiple stacked ProjectSet nodes. The ProjectSet nodes always get
input from an underlying node.
We also discussed and prototyped evaluating targetlist SRFs using ROWS
FROM(), but that turned out to be more complicated than we'd hoped.
While moving SRF evaluation to ProjectSet would allow to retain the old
"least common multiple" behavior when multiple SRFs are present in one
targetlist (i.e. continue returning rows until all SRFs are at the end of
their input at the same time), we decided to instead only return rows till
all SRFs are exhausted, returning NULL for already exhausted ones. We
deemed the previous behavior to be too confusing, unexpected and actually
not particularly useful.
As a side effect, the previously prohibited case of multiple set returning
arguments to a function, is now allowed. Not because it's particularly
desirable, but because it ends up working and there seems to be no argument
for adding code to prohibit it.
Currently the behavior for COALESCE and CASE containing SRFs has changed,
returning multiple rows from the expression, even when the SRF containing
"arm" of the expression is not evaluated. That's because the SRFs are
evaluated in a separate ProjectSet node. As that's quite confusing, we're
likely to instead prohibit SRFs in those places. But that's still being
discussed, and the code would reside in places not touched here, so that's
a task for later.
There's a lot of, now superfluous, code dealing with set return expressions
around. But as the changes to get rid of those are verbose largely boring,
it seems better for readability to keep the cleanup as a separate commit.
Author: Tom Lane and Andres Freund
Discussion: https://postgr.es/m/20160822214023.aaxz5l4igypowyri@alap3.anarazel.de
9 years ago
|
|
|
case T_ProjectSet:
|
|
|
|
|
result = (PlanState *) ExecInitProjectSet((ProjectSet *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_ModifyTable:
|
|
|
|
|
result = (PlanState *) ExecInitModifyTable((ModifyTable *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_Append:
|
|
|
|
|
result = (PlanState *) ExecInitAppend((Append *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_MergeAppend:
|
|
|
|
|
result = (PlanState *) ExecInitMergeAppend((MergeAppend *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_RecursiveUnion:
|
|
|
|
|
result = (PlanState *) ExecInitRecursiveUnion((RecursiveUnion *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_BitmapAnd:
|
|
|
|
|
result = (PlanState *) ExecInitBitmapAnd((BitmapAnd *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_BitmapOr:
|
|
|
|
|
result = (PlanState *) ExecInitBitmapOr((BitmapOr *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* scan nodes
|
|
|
|
|
*/
|
|
|
|
|
case T_SeqScan:
|
|
|
|
|
result = (PlanState *) ExecInitSeqScan((SeqScan *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_SampleScan:
|
|
|
|
|
result = (PlanState *) ExecInitSampleScan((SampleScan *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_IndexScan:
|
|
|
|
|
result = (PlanState *) ExecInitIndexScan((IndexScan *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_IndexOnlyScan:
|
|
|
|
|
result = (PlanState *) ExecInitIndexOnlyScan((IndexOnlyScan *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_BitmapIndexScan:
|
|
|
|
|
result = (PlanState *) ExecInitBitmapIndexScan((BitmapIndexScan *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_BitmapHeapScan:
|
|
|
|
|
result = (PlanState *) ExecInitBitmapHeapScan((BitmapHeapScan *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_TidScan:
|
|
|
|
|
result = (PlanState *) ExecInitTidScan((TidScan *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_SubqueryScan:
|
|
|
|
|
result = (PlanState *) ExecInitSubqueryScan((SubqueryScan *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_FunctionScan:
|
|
|
|
|
result = (PlanState *) ExecInitFunctionScan((FunctionScan *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_TableFuncScan:
|
|
|
|
|
result = (PlanState *) ExecInitTableFuncScan((TableFuncScan *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_ValuesScan:
|
|
|
|
|
result = (PlanState *) ExecInitValuesScan((ValuesScan *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_CteScan:
|
|
|
|
|
result = (PlanState *) ExecInitCteScan((CteScan *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_WorkTableScan:
|
|
|
|
|
result = (PlanState *) ExecInitWorkTableScan((WorkTableScan *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_ForeignScan:
|
|
|
|
|
result = (PlanState *) ExecInitForeignScan((ForeignScan *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_CustomScan:
|
|
|
|
|
result = (PlanState *) ExecInitCustomScan((CustomScan *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* join nodes
|
|
|
|
|
*/
|
|
|
|
|
case T_NestLoop:
|
|
|
|
|
result = (PlanState *) ExecInitNestLoop((NestLoop *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_MergeJoin:
|
|
|
|
|
result = (PlanState *) ExecInitMergeJoin((MergeJoin *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_HashJoin:
|
|
|
|
|
result = (PlanState *) ExecInitHashJoin((HashJoin *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* materialization nodes
|
|
|
|
|
*/
|
|
|
|
|
case T_Material:
|
|
|
|
|
result = (PlanState *) ExecInitMaterial((Material *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_Sort:
|
|
|
|
|
result = (PlanState *) ExecInitSort((Sort *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_Group:
|
|
|
|
|
result = (PlanState *) ExecInitGroup((Group *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_Agg:
|
|
|
|
|
result = (PlanState *) ExecInitAgg((Agg *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_WindowAgg:
|
|
|
|
|
result = (PlanState *) ExecInitWindowAgg((WindowAgg *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_Unique:
|
|
|
|
|
result = (PlanState *) ExecInitUnique((Unique *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
Add a Gather executor node.
A Gather executor node runs any number of copies of a plan in an equal
number of workers and merges all of the results into a single tuple
stream. It can also run the plan itself, if the workers are
unavailable or haven't started up yet. It is intended to work with
the Partial Seq Scan node which will be added in future commits.
It could also be used to implement parallel query of a different sort
by itself, without help from Partial Seq Scan, if the single_copy mode
is used. In that mode, a worker executes the plan, and the parallel
leader does not, merely collecting the worker's results. So, a Gather
node could be inserted into a plan to split the execution of that plan
across two processes. Nested Gather nodes aren't currently supported,
but we might want to add support for that in the future.
There's nothing in the planner to actually generate Gather nodes yet,
so it's not quite time to break out the champagne. But we're getting
close.
Amit Kapila. Some designs suggestions were provided by me, and I also
reviewed the patch. Single-copy mode, documentation, and other minor
changes also by me.
10 years ago
|
|
|
case T_Gather:
|
|
|
|
|
result = (PlanState *) ExecInitGather((Gather *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_Hash:
|
|
|
|
|
result = (PlanState *) ExecInitHash((Hash *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_SetOp:
|
|
|
|
|
result = (PlanState *) ExecInitSetOp((SetOp *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_LockRows:
|
|
|
|
|
result = (PlanState *) ExecInitLockRows((LockRows *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_Limit:
|
|
|
|
|
result = (PlanState *) ExecInitLimit((Limit *) node,
|
|
|
|
|
estate, eflags);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
default:
|
|
|
|
|
elog(ERROR, "unrecognized node type: %d", (int) nodeTag(node));
|
|
|
|
|
result = NULL; /* keep compiler quiet */
|
|
|
|
|
break;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Initialize any initPlans present in this node. The planner put them in
|
|
|
|
|
* a separate list for us.
|
|
|
|
|
*/
|
|
|
|
|
subps = NIL;
|
|
|
|
|
foreach(l, node->initPlan)
|
|
|
|
|
{
|
|
|
|
|
SubPlan *subplan = (SubPlan *) lfirst(l);
|
|
|
|
|
SubPlanState *sstate;
|
|
|
|
|
|
|
|
|
|
Assert(IsA(subplan, SubPlan));
|
|
|
|
|
sstate = ExecInitSubPlan(subplan, result);
|
|
|
|
|
subps = lappend(subps, sstate);
|
|
|
|
|
}
|
|
|
|
|
result->initPlan = subps;
|
|
|
|
|
|
|
|
|
|
/* Set up instrumentation for this node if requested */
|
|
|
|
|
if (estate->es_instrument)
|
|
|
|
|
result->instrument = InstrAlloc(1, estate->es_instrument);
|
|
|
|
|
|
|
|
|
|
return result;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/* ----------------------------------------------------------------
|
|
|
|
|
* ExecProcNode
|
|
|
|
|
*
|
|
|
|
|
* Execute the given node to return a(nother) tuple.
|
|
|
|
|
* ----------------------------------------------------------------
|
|
|
|
|
*/
|
|
|
|
|
TupleTableSlot *
|
|
|
|
|
ExecProcNode(PlanState *node)
|
|
|
|
|
{
|
|
|
|
|
TupleTableSlot *result;
|
|
|
|
|
|
|
|
|
|
CHECK_FOR_INTERRUPTS();
|
|
|
|
|
|
|
|
|
|
if (node->chgParam != NULL) /* something changed */
|
|
|
|
|
ExecReScan(node); /* let ReScan handle this */
|
|
|
|
|
|
|
|
|
|
if (node->instrument)
|
|
|
|
|
InstrStartNode(node->instrument);
|
|
|
|
|
|
|
|
|
|
switch (nodeTag(node))
|
|
|
|
|
{
|
|
|
|
|
/*
|
|
|
|
|
* control nodes
|
|
|
|
|
*/
|
|
|
|
|
case T_ResultState:
|
|
|
|
|
result = ExecResult((ResultState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
Move targetlist SRF handling from expression evaluation to new executor node.
Evaluation of set returning functions (SRFs_ in the targetlist (like SELECT
generate_series(1,5)) so far was done in the expression evaluation (i.e.
ExecEvalExpr()) and projection (i.e. ExecProject/ExecTargetList) code.
This meant that most executor nodes performing projection, and most
expression evaluation functions, had to deal with the possibility that an
evaluated expression could return a set of return values.
That's bad because it leads to repeated code in a lot of places. It also,
and that's my (Andres's) motivation, made it a lot harder to implement a
more efficient way of doing expression evaluation.
To fix this, introduce a new executor node (ProjectSet) that can evaluate
targetlists containing one or more SRFs. To avoid the complexity of the old
way of handling nested expressions returning sets (e.g. having to pass up
ExprDoneCond, and dealing with arguments to functions returning sets etc.),
those SRFs can only be at the top level of the node's targetlist. The
planner makes sure (via split_pathtarget_at_srfs()) that SRF evaluation is
only necessary in ProjectSet nodes and that SRFs are only present at the
top level of the node's targetlist. If there are nested SRFs the planner
creates multiple stacked ProjectSet nodes. The ProjectSet nodes always get
input from an underlying node.
We also discussed and prototyped evaluating targetlist SRFs using ROWS
FROM(), but that turned out to be more complicated than we'd hoped.
While moving SRF evaluation to ProjectSet would allow to retain the old
"least common multiple" behavior when multiple SRFs are present in one
targetlist (i.e. continue returning rows until all SRFs are at the end of
their input at the same time), we decided to instead only return rows till
all SRFs are exhausted, returning NULL for already exhausted ones. We
deemed the previous behavior to be too confusing, unexpected and actually
not particularly useful.
As a side effect, the previously prohibited case of multiple set returning
arguments to a function, is now allowed. Not because it's particularly
desirable, but because it ends up working and there seems to be no argument
for adding code to prohibit it.
Currently the behavior for COALESCE and CASE containing SRFs has changed,
returning multiple rows from the expression, even when the SRF containing
"arm" of the expression is not evaluated. That's because the SRFs are
evaluated in a separate ProjectSet node. As that's quite confusing, we're
likely to instead prohibit SRFs in those places. But that's still being
discussed, and the code would reside in places not touched here, so that's
a task for later.
There's a lot of, now superfluous, code dealing with set return expressions
around. But as the changes to get rid of those are verbose largely boring,
it seems better for readability to keep the cleanup as a separate commit.
Author: Tom Lane and Andres Freund
Discussion: https://postgr.es/m/20160822214023.aaxz5l4igypowyri@alap3.anarazel.de
9 years ago
|
|
|
case T_ProjectSetState:
|
|
|
|
|
result = ExecProjectSet((ProjectSetState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_ModifyTableState:
|
|
|
|
|
result = ExecModifyTable((ModifyTableState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_AppendState:
|
|
|
|
|
result = ExecAppend((AppendState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_MergeAppendState:
|
|
|
|
|
result = ExecMergeAppend((MergeAppendState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_RecursiveUnionState:
|
|
|
|
|
result = ExecRecursiveUnion((RecursiveUnionState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
/* BitmapAndState does not yield tuples */
|
|
|
|
|
|
|
|
|
|
/* BitmapOrState does not yield tuples */
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* scan nodes
|
|
|
|
|
*/
|
|
|
|
|
case T_SeqScanState:
|
|
|
|
|
result = ExecSeqScan((SeqScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_SampleScanState:
|
|
|
|
|
result = ExecSampleScan((SampleScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_IndexScanState:
|
|
|
|
|
result = ExecIndexScan((IndexScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_IndexOnlyScanState:
|
|
|
|
|
result = ExecIndexOnlyScan((IndexOnlyScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
/* BitmapIndexScanState does not yield tuples */
|
|
|
|
|
|
|
|
|
|
case T_BitmapHeapScanState:
|
|
|
|
|
result = ExecBitmapHeapScan((BitmapHeapScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_TidScanState:
|
|
|
|
|
result = ExecTidScan((TidScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_SubqueryScanState:
|
|
|
|
|
result = ExecSubqueryScan((SubqueryScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_FunctionScanState:
|
|
|
|
|
result = ExecFunctionScan((FunctionScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_TableFuncScanState:
|
|
|
|
|
result = ExecTableFuncScan((TableFuncScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_ValuesScanState:
|
|
|
|
|
result = ExecValuesScan((ValuesScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_CteScanState:
|
|
|
|
|
result = ExecCteScan((CteScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_WorkTableScanState:
|
|
|
|
|
result = ExecWorkTableScan((WorkTableScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_ForeignScanState:
|
|
|
|
|
result = ExecForeignScan((ForeignScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_CustomScanState:
|
|
|
|
|
result = ExecCustomScan((CustomScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* join nodes
|
|
|
|
|
*/
|
|
|
|
|
case T_NestLoopState:
|
|
|
|
|
result = ExecNestLoop((NestLoopState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_MergeJoinState:
|
|
|
|
|
result = ExecMergeJoin((MergeJoinState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_HashJoinState:
|
|
|
|
|
result = ExecHashJoin((HashJoinState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* materialization nodes
|
|
|
|
|
*/
|
|
|
|
|
case T_MaterialState:
|
|
|
|
|
result = ExecMaterial((MaterialState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_SortState:
|
|
|
|
|
result = ExecSort((SortState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_GroupState:
|
|
|
|
|
result = ExecGroup((GroupState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_AggState:
|
|
|
|
|
result = ExecAgg((AggState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_WindowAggState:
|
|
|
|
|
result = ExecWindowAgg((WindowAggState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_UniqueState:
|
|
|
|
|
result = ExecUnique((UniqueState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
Add a Gather executor node.
A Gather executor node runs any number of copies of a plan in an equal
number of workers and merges all of the results into a single tuple
stream. It can also run the plan itself, if the workers are
unavailable or haven't started up yet. It is intended to work with
the Partial Seq Scan node which will be added in future commits.
It could also be used to implement parallel query of a different sort
by itself, without help from Partial Seq Scan, if the single_copy mode
is used. In that mode, a worker executes the plan, and the parallel
leader does not, merely collecting the worker's results. So, a Gather
node could be inserted into a plan to split the execution of that plan
across two processes. Nested Gather nodes aren't currently supported,
but we might want to add support for that in the future.
There's nothing in the planner to actually generate Gather nodes yet,
so it's not quite time to break out the champagne. But we're getting
close.
Amit Kapila. Some designs suggestions were provided by me, and I also
reviewed the patch. Single-copy mode, documentation, and other minor
changes also by me.
10 years ago
|
|
|
case T_GatherState:
|
|
|
|
|
result = ExecGather((GatherState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_HashState:
|
|
|
|
|
result = ExecHash((HashState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_SetOpState:
|
|
|
|
|
result = ExecSetOp((SetOpState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_LockRowsState:
|
|
|
|
|
result = ExecLockRows((LockRowsState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_LimitState:
|
|
|
|
|
result = ExecLimit((LimitState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
default:
|
|
|
|
|
elog(ERROR, "unrecognized node type: %d", (int) nodeTag(node));
|
|
|
|
|
result = NULL;
|
|
|
|
|
break;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
if (node->instrument)
|
|
|
|
|
InstrStopNode(node->instrument, TupIsNull(result) ? 0.0 : 1.0);
|
|
|
|
|
|
|
|
|
|
return result;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/* ----------------------------------------------------------------
|
|
|
|
|
* MultiExecProcNode
|
|
|
|
|
*
|
|
|
|
|
* Execute a node that doesn't return individual tuples
|
|
|
|
|
* (it might return a hashtable, bitmap, etc). Caller should
|
|
|
|
|
* check it got back the expected kind of Node.
|
|
|
|
|
*
|
|
|
|
|
* This has essentially the same responsibilities as ExecProcNode,
|
|
|
|
|
* but it does not do InstrStartNode/InstrStopNode (mainly because
|
|
|
|
|
* it can't tell how many returned tuples to count). Each per-node
|
|
|
|
|
* function must provide its own instrumentation support.
|
|
|
|
|
* ----------------------------------------------------------------
|
|
|
|
|
*/
|
|
|
|
|
Node *
|
|
|
|
|
MultiExecProcNode(PlanState *node)
|
|
|
|
|
{
|
|
|
|
|
Node *result;
|
|
|
|
|
|
|
|
|
|
CHECK_FOR_INTERRUPTS();
|
|
|
|
|
|
|
|
|
|
if (node->chgParam != NULL) /* something changed */
|
|
|
|
|
ExecReScan(node); /* let ReScan handle this */
|
|
|
|
|
|
|
|
|
|
switch (nodeTag(node))
|
|
|
|
|
{
|
|
|
|
|
/*
|
|
|
|
|
* Only node types that actually support multiexec will be listed
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
case T_HashState:
|
|
|
|
|
result = MultiExecHash((HashState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_BitmapIndexScanState:
|
|
|
|
|
result = MultiExecBitmapIndexScan((BitmapIndexScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_BitmapAndState:
|
|
|
|
|
result = MultiExecBitmapAnd((BitmapAndState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_BitmapOrState:
|
|
|
|
|
result = MultiExecBitmapOr((BitmapOrState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
default:
|
|
|
|
|
elog(ERROR, "unrecognized node type: %d", (int) nodeTag(node));
|
|
|
|
|
result = NULL;
|
|
|
|
|
break;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return result;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/* ----------------------------------------------------------------
|
|
|
|
|
* ExecEndNode
|
|
|
|
|
*
|
|
|
|
|
* Recursively cleans up all the nodes in the plan rooted
|
|
|
|
|
* at 'node'.
|
|
|
|
|
*
|
|
|
|
|
* After this operation, the query plan will not be able to be
|
|
|
|
|
* processed any further. This should be called only after
|
|
|
|
|
* the query plan has been fully executed.
|
|
|
|
|
* ----------------------------------------------------------------
|
|
|
|
|
*/
|
|
|
|
|
void
|
|
|
|
|
ExecEndNode(PlanState *node)
|
|
|
|
|
{
|
|
|
|
|
/*
|
|
|
|
|
* do nothing when we get to the end of a leaf on tree.
|
|
|
|
|
*/
|
|
|
|
|
if (node == NULL)
|
|
|
|
|
return;
|
|
|
|
|
|
|
|
|
|
if (node->chgParam != NULL)
|
|
|
|
|
{
|
|
|
|
|
bms_free(node->chgParam);
|
|
|
|
|
node->chgParam = NULL;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
switch (nodeTag(node))
|
|
|
|
|
{
|
|
|
|
|
/*
|
|
|
|
|
* control nodes
|
|
|
|
|
*/
|
|
|
|
|
case T_ResultState:
|
|
|
|
|
ExecEndResult((ResultState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
Move targetlist SRF handling from expression evaluation to new executor node.
Evaluation of set returning functions (SRFs_ in the targetlist (like SELECT
generate_series(1,5)) so far was done in the expression evaluation (i.e.
ExecEvalExpr()) and projection (i.e. ExecProject/ExecTargetList) code.
This meant that most executor nodes performing projection, and most
expression evaluation functions, had to deal with the possibility that an
evaluated expression could return a set of return values.
That's bad because it leads to repeated code in a lot of places. It also,
and that's my (Andres's) motivation, made it a lot harder to implement a
more efficient way of doing expression evaluation.
To fix this, introduce a new executor node (ProjectSet) that can evaluate
targetlists containing one or more SRFs. To avoid the complexity of the old
way of handling nested expressions returning sets (e.g. having to pass up
ExprDoneCond, and dealing with arguments to functions returning sets etc.),
those SRFs can only be at the top level of the node's targetlist. The
planner makes sure (via split_pathtarget_at_srfs()) that SRF evaluation is
only necessary in ProjectSet nodes and that SRFs are only present at the
top level of the node's targetlist. If there are nested SRFs the planner
creates multiple stacked ProjectSet nodes. The ProjectSet nodes always get
input from an underlying node.
We also discussed and prototyped evaluating targetlist SRFs using ROWS
FROM(), but that turned out to be more complicated than we'd hoped.
While moving SRF evaluation to ProjectSet would allow to retain the old
"least common multiple" behavior when multiple SRFs are present in one
targetlist (i.e. continue returning rows until all SRFs are at the end of
their input at the same time), we decided to instead only return rows till
all SRFs are exhausted, returning NULL for already exhausted ones. We
deemed the previous behavior to be too confusing, unexpected and actually
not particularly useful.
As a side effect, the previously prohibited case of multiple set returning
arguments to a function, is now allowed. Not because it's particularly
desirable, but because it ends up working and there seems to be no argument
for adding code to prohibit it.
Currently the behavior for COALESCE and CASE containing SRFs has changed,
returning multiple rows from the expression, even when the SRF containing
"arm" of the expression is not evaluated. That's because the SRFs are
evaluated in a separate ProjectSet node. As that's quite confusing, we're
likely to instead prohibit SRFs in those places. But that's still being
discussed, and the code would reside in places not touched here, so that's
a task for later.
There's a lot of, now superfluous, code dealing with set return expressions
around. But as the changes to get rid of those are verbose largely boring,
it seems better for readability to keep the cleanup as a separate commit.
Author: Tom Lane and Andres Freund
Discussion: https://postgr.es/m/20160822214023.aaxz5l4igypowyri@alap3.anarazel.de
9 years ago
|
|
|
case T_ProjectSetState:
|
|
|
|
|
ExecEndProjectSet((ProjectSetState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_ModifyTableState:
|
|
|
|
|
ExecEndModifyTable((ModifyTableState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_AppendState:
|
|
|
|
|
ExecEndAppend((AppendState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_MergeAppendState:
|
|
|
|
|
ExecEndMergeAppend((MergeAppendState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_RecursiveUnionState:
|
|
|
|
|
ExecEndRecursiveUnion((RecursiveUnionState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_BitmapAndState:
|
|
|
|
|
ExecEndBitmapAnd((BitmapAndState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_BitmapOrState:
|
|
|
|
|
ExecEndBitmapOr((BitmapOrState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* scan nodes
|
|
|
|
|
*/
|
|
|
|
|
case T_SeqScanState:
|
|
|
|
|
ExecEndSeqScan((SeqScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_SampleScanState:
|
|
|
|
|
ExecEndSampleScan((SampleScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
Add a Gather executor node.
A Gather executor node runs any number of copies of a plan in an equal
number of workers and merges all of the results into a single tuple
stream. It can also run the plan itself, if the workers are
unavailable or haven't started up yet. It is intended to work with
the Partial Seq Scan node which will be added in future commits.
It could also be used to implement parallel query of a different sort
by itself, without help from Partial Seq Scan, if the single_copy mode
is used. In that mode, a worker executes the plan, and the parallel
leader does not, merely collecting the worker's results. So, a Gather
node could be inserted into a plan to split the execution of that plan
across two processes. Nested Gather nodes aren't currently supported,
but we might want to add support for that in the future.
There's nothing in the planner to actually generate Gather nodes yet,
so it's not quite time to break out the champagne. But we're getting
close.
Amit Kapila. Some designs suggestions were provided by me, and I also
reviewed the patch. Single-copy mode, documentation, and other minor
changes also by me.
10 years ago
|
|
|
case T_GatherState:
|
|
|
|
|
ExecEndGather((GatherState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_IndexScanState:
|
|
|
|
|
ExecEndIndexScan((IndexScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_IndexOnlyScanState:
|
|
|
|
|
ExecEndIndexOnlyScan((IndexOnlyScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_BitmapIndexScanState:
|
|
|
|
|
ExecEndBitmapIndexScan((BitmapIndexScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_BitmapHeapScanState:
|
|
|
|
|
ExecEndBitmapHeapScan((BitmapHeapScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_TidScanState:
|
|
|
|
|
ExecEndTidScan((TidScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_SubqueryScanState:
|
|
|
|
|
ExecEndSubqueryScan((SubqueryScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_FunctionScanState:
|
|
|
|
|
ExecEndFunctionScan((FunctionScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_TableFuncScanState:
|
|
|
|
|
ExecEndTableFuncScan((TableFuncScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_ValuesScanState:
|
|
|
|
|
ExecEndValuesScan((ValuesScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_CteScanState:
|
|
|
|
|
ExecEndCteScan((CteScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_WorkTableScanState:
|
|
|
|
|
ExecEndWorkTableScan((WorkTableScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_ForeignScanState:
|
|
|
|
|
ExecEndForeignScan((ForeignScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_CustomScanState:
|
|
|
|
|
ExecEndCustomScan((CustomScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* join nodes
|
|
|
|
|
*/
|
|
|
|
|
case T_NestLoopState:
|
|
|
|
|
ExecEndNestLoop((NestLoopState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_MergeJoinState:
|
|
|
|
|
ExecEndMergeJoin((MergeJoinState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_HashJoinState:
|
|
|
|
|
ExecEndHashJoin((HashJoinState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* materialization nodes
|
|
|
|
|
*/
|
|
|
|
|
case T_MaterialState:
|
|
|
|
|
ExecEndMaterial((MaterialState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_SortState:
|
|
|
|
|
ExecEndSort((SortState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_GroupState:
|
|
|
|
|
ExecEndGroup((GroupState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_AggState:
|
|
|
|
|
ExecEndAgg((AggState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_WindowAggState:
|
|
|
|
|
ExecEndWindowAgg((WindowAggState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_UniqueState:
|
|
|
|
|
ExecEndUnique((UniqueState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_HashState:
|
|
|
|
|
ExecEndHash((HashState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_SetOpState:
|
|
|
|
|
ExecEndSetOp((SetOpState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_LockRowsState:
|
|
|
|
|
ExecEndLockRows((LockRowsState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
case T_LimitState:
|
|
|
|
|
ExecEndLimit((LimitState *) node);
|
|
|
|
|
break;
|
|
|
|
|
|
|
|
|
|
default:
|
|
|
|
|
elog(ERROR, "unrecognized node type: %d", (int) nodeTag(node));
|
|
|
|
|
break;
|
|
|
|
|
}
|
|
|
|
|
}
|
Add a Gather executor node.
A Gather executor node runs any number of copies of a plan in an equal
number of workers and merges all of the results into a single tuple
stream. It can also run the plan itself, if the workers are
unavailable or haven't started up yet. It is intended to work with
the Partial Seq Scan node which will be added in future commits.
It could also be used to implement parallel query of a different sort
by itself, without help from Partial Seq Scan, if the single_copy mode
is used. In that mode, a worker executes the plan, and the parallel
leader does not, merely collecting the worker's results. So, a Gather
node could be inserted into a plan to split the execution of that plan
across two processes. Nested Gather nodes aren't currently supported,
but we might want to add support for that in the future.
There's nothing in the planner to actually generate Gather nodes yet,
so it's not quite time to break out the champagne. But we're getting
close.
Amit Kapila. Some designs suggestions were provided by me, and I also
reviewed the patch. Single-copy mode, documentation, and other minor
changes also by me.
10 years ago
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* ExecShutdownNode
|
|
|
|
|
*
|
|
|
|
|
* Give execution nodes a chance to stop asynchronous resource consumption
|
|
|
|
|
* and release any resources still held. Currently, this is only used for
|
|
|
|
|
* parallel query, but we might want to extend it to other cases also (e.g.
|
|
|
|
|
* FDW). We might also want to call it sooner, as soon as it's evident that
|
|
|
|
|
* no more rows will be needed (e.g. when a Limit is filled) rather than only
|
|
|
|
|
* at the end of ExecutorRun.
|
|
|
|
|
*/
|
|
|
|
|
bool
|
|
|
|
|
ExecShutdownNode(PlanState *node)
|
|
|
|
|
{
|
|
|
|
|
if (node == NULL)
|
|
|
|
|
return false;
|
|
|
|
|
|
|
|
|
|
planstate_tree_walker(node, ExecShutdownNode, NULL);
|
|
|
|
|
|
Add a Gather executor node.
A Gather executor node runs any number of copies of a plan in an equal
number of workers and merges all of the results into a single tuple
stream. It can also run the plan itself, if the workers are
unavailable or haven't started up yet. It is intended to work with
the Partial Seq Scan node which will be added in future commits.
It could also be used to implement parallel query of a different sort
by itself, without help from Partial Seq Scan, if the single_copy mode
is used. In that mode, a worker executes the plan, and the parallel
leader does not, merely collecting the worker's results. So, a Gather
node could be inserted into a plan to split the execution of that plan
across two processes. Nested Gather nodes aren't currently supported,
but we might want to add support for that in the future.
There's nothing in the planner to actually generate Gather nodes yet,
so it's not quite time to break out the champagne. But we're getting
close.
Amit Kapila. Some designs suggestions were provided by me, and I also
reviewed the patch. Single-copy mode, documentation, and other minor
changes also by me.
10 years ago
|
|
|
switch (nodeTag(node))
|
|
|
|
|
{
|
|
|
|
|
case T_GatherState:
|
|
|
|
|
ExecShutdownGather((GatherState *) node);
|
Add a Gather executor node.
A Gather executor node runs any number of copies of a plan in an equal
number of workers and merges all of the results into a single tuple
stream. It can also run the plan itself, if the workers are
unavailable or haven't started up yet. It is intended to work with
the Partial Seq Scan node which will be added in future commits.
It could also be used to implement parallel query of a different sort
by itself, without help from Partial Seq Scan, if the single_copy mode
is used. In that mode, a worker executes the plan, and the parallel
leader does not, merely collecting the worker's results. So, a Gather
node could be inserted into a plan to split the execution of that plan
across two processes. Nested Gather nodes aren't currently supported,
but we might want to add support for that in the future.
There's nothing in the planner to actually generate Gather nodes yet,
so it's not quite time to break out the champagne. But we're getting
close.
Amit Kapila. Some designs suggestions were provided by me, and I also
reviewed the patch. Single-copy mode, documentation, and other minor
changes also by me.
10 years ago
|
|
|
break;
|
|
|
|
|
case T_ForeignScanState:
|
|
|
|
|
ExecShutdownForeignScan((ForeignScanState *) node);
|
|
|
|
|
break;
|
|
|
|
|
case T_CustomScanState:
|
|
|
|
|
ExecShutdownCustomScan((CustomScanState *) node);
|
|
|
|
|
break;
|
Add a Gather executor node.
A Gather executor node runs any number of copies of a plan in an equal
number of workers and merges all of the results into a single tuple
stream. It can also run the plan itself, if the workers are
unavailable or haven't started up yet. It is intended to work with
the Partial Seq Scan node which will be added in future commits.
It could also be used to implement parallel query of a different sort
by itself, without help from Partial Seq Scan, if the single_copy mode
is used. In that mode, a worker executes the plan, and the parallel
leader does not, merely collecting the worker's results. So, a Gather
node could be inserted into a plan to split the execution of that plan
across two processes. Nested Gather nodes aren't currently supported,
but we might want to add support for that in the future.
There's nothing in the planner to actually generate Gather nodes yet,
so it's not quite time to break out the champagne. But we're getting
close.
Amit Kapila. Some designs suggestions were provided by me, and I also
reviewed the patch. Single-copy mode, documentation, and other minor
changes also by me.
10 years ago
|
|
|
default:
|
|
|
|
|
break;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return false;
|
Add a Gather executor node.
A Gather executor node runs any number of copies of a plan in an equal
number of workers and merges all of the results into a single tuple
stream. It can also run the plan itself, if the workers are
unavailable or haven't started up yet. It is intended to work with
the Partial Seq Scan node which will be added in future commits.
It could also be used to implement parallel query of a different sort
by itself, without help from Partial Seq Scan, if the single_copy mode
is used. In that mode, a worker executes the plan, and the parallel
leader does not, merely collecting the worker's results. So, a Gather
node could be inserted into a plan to split the execution of that plan
across two processes. Nested Gather nodes aren't currently supported,
but we might want to add support for that in the future.
There's nothing in the planner to actually generate Gather nodes yet,
so it's not quite time to break out the champagne. But we're getting
close.
Amit Kapila. Some designs suggestions were provided by me, and I also
reviewed the patch. Single-copy mode, documentation, and other minor
changes also by me.
10 years ago
|
|
|
}
|
