Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit3030189

Browse files
committed
Fix erroneous handling of parameters at SubqueryScan plan nodes,
per bug report from Don Baccus.
1 parent712af72 commit3030189

File tree

1 file changed

+9
-2
lines changed

1 file changed

+9
-2
lines changed

‎src/backend/optimizer/plan/subselect.c

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
* Portions Copyright (c) 1994, Regents of the University of California
88
*
99
* IDENTIFICATION
10-
* $Header: /cvsroot/pgsql/src/backend/optimizer/plan/subselect.c,v 1.45 2000/11/16 22:30:25 tgl Exp $
10+
* $Header: /cvsroot/pgsql/src/backend/optimizer/plan/subselect.c,v 1.46 2000/11/21 00:17:59 tgl Exp $
1111
*
1212
*-------------------------------------------------------------------------
1313
*/
@@ -613,8 +613,15 @@ SS_finalize_plan(Plan *plan)
613613
break;
614614

615615
caseT_SubqueryScan:
616+
/*
617+
* In a SubqueryScan, SS_finalize_plan has already been run
618+
* on the subplan by the inner invocation of subquery_planner,
619+
* so there's no need to do it again. Instead, just pull out
620+
* the subplan's extParams list, which represents the params
621+
* it needs from my level and higher levels.
622+
*/
616623
results.paramids=set_unioni(results.paramids,
617-
SS_finalize_plan(((SubqueryScan*)plan)->subplan));
624+
((SubqueryScan*)plan)->subplan->extParam);
618625
break;
619626

620627
caseT_IndexScan:

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp