diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2006-12-26 19:26:46 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2006-12-26 19:26:46 +0000 |
| commit | 68996463d405a0e3e35f81371ffebbbaff7c1f63 (patch) | |
| tree | 1393ccac93c28d38880e78594e78da571185ea99 /src/backend/executor/nodeFunctionscan.c | |
| parent | fccf99f0c81ac2ad9af6e6fa746375c39ca7ab0b (diff) | |
| download | postgresql-68996463d405a0e3e35f81371ffebbbaff7c1f63.tar.gz postgresql-68996463d405a0e3e35f81371ffebbbaff7c1f63.zip | |
Repair bug #2839: the various ExecReScan functions need to reset
ps_TupFromTlist in plan nodes that make use of it. This was being done
correctly in join nodes and Result nodes but not in any relation-scan nodes.
Bug would lead to bogus results if a set-returning function appeared in the
targetlist of a subquery that could be rescanned after partial execution,
for example a subquery within EXISTS(). Bug has been around forever :-(
... surprising it wasn't reported before.
Diffstat (limited to 'src/backend/executor/nodeFunctionscan.c')
| -rw-r--r-- | src/backend/executor/nodeFunctionscan.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/src/backend/executor/nodeFunctionscan.c b/src/backend/executor/nodeFunctionscan.c index 90ab0188743..01aa072610b 100644 --- a/src/backend/executor/nodeFunctionscan.c +++ b/src/backend/executor/nodeFunctionscan.c @@ -8,7 +8,7 @@ * * * IDENTIFICATION - * $PostgreSQL: pgsql/src/backend/executor/nodeFunctionscan.c,v 1.40 2006/06/27 02:51:39 tgl Exp $ + * $PostgreSQL: pgsql/src/backend/executor/nodeFunctionscan.c,v 1.41 2006/12/26 19:26:45 tgl Exp $ * *------------------------------------------------------------------------- */ @@ -317,6 +317,7 @@ void ExecFunctionReScan(FunctionScanState *node, ExprContext *exprCtxt) { ExecClearTuple(node->ss.ps.ps_ResultTupleSlot); + node->ss.ps.ps_TupFromTlist = false; /* * If we haven't materialized yet, just return. |