c8h4/postgresql
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix erroneous handling of parameters at SubqueryScan plan nodes,

Browse source 
per bug report from Don Baccus.
This commit is contained in:
Tom Lane 2000-11-21 00:17:59 +00:00
parent 712af72c77
commit 3030189b69
1 changed files with 9 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
src/backend/optimizer/plan/subselect.c
View file

@ -7,7 +7,7 @@
* Portions Copyright (c) 1994, Regents of the University of California
*
* IDENTIFICATION
* $Header: /cvsroot/pgsql/src/backend/optimizer/plan/subselect.c,v 1.45 2000/11/16 22:30:25 tgl Exp $
* $Header: /cvsroot/pgsql/src/backend/optimizer/plan/subselect.c,v 1.46 2000/11/21 00:17:59 tgl Exp $
*
*-------------------------------------------------------------------------
*/
@ -613,8 +613,15 @@ SS_finalize_plan(Plan *plan)
break;
case T_SubqueryScan:
/*
* In a SubqueryScan, SS_finalize_plan has already been run
* on the subplan by the inner invocation of subquery_planner,
* so there's no need to do it again. Instead, just pull out
* the subplan's extParams list, which represents the params
* it needs from my level and higher levels.
*/
results.paramids = set_unioni(results.paramids,
SS_finalize_plan(((SubqueryScan *) plan)->subplan));
((SubqueryScan *) plan)->subplan->extParam);
break;
case T_IndexScan: