diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2006-12-26 19:27:20 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2006-12-26 19:27:20 +0000 |
| commit | 0fbfdf55f82cec91bd3cd1ba136e29f85f359a1a (patch) | |
| tree | 0348841bb1789affefb2e029b27f3ec89de85a28 /src/backend/executor/nodeFunctionscan.c | |
| parent | 8eb0f23a961e4c6e08191d8bf6c2a805d0c71eff (diff) | |
| download | postgresql-0fbfdf55f82cec91bd3cd1ba136e29f85f359a1a.tar.gz postgresql-0fbfdf55f82cec91bd3cd1ba136e29f85f359a1a.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 a47e37d7e55..f39eaeff04a 100644 --- a/src/backend/executor/nodeFunctionscan.c +++ b/src/backend/executor/nodeFunctionscan.c @@ -8,7 +8,7 @@ * * * IDENTIFICATION - * $Header: /cvsroot/pgsql/src/backend/executor/nodeFunctionscan.c,v 1.22 2003/09/25 23:02:12 tgl Exp $ + * $Header: /cvsroot/pgsql/src/backend/executor/nodeFunctionscan.c,v 1.22.2.1 2006/12/26 19:27:20 tgl Exp $ * *------------------------------------------------------------------------- */ @@ -341,6 +341,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. |