|
7 | 7 | * Portions Copyright (c) 1994, Regents of the University of California |
8 | 8 | * |
9 | 9 | * IDENTIFICATION |
10 | | - * $PostgreSQL: pgsql/src/backend/optimizer/plan/subselect.c,v 1.135 2008/08/17 02:19:19 tgl Exp $ |
| 10 | + * $PostgreSQL: pgsql/src/backend/optimizer/plan/subselect.c,v 1.136 2008/08/20 15:49:30 tgl Exp $ |
11 | 11 | * |
12 | 12 | *------------------------------------------------------------------------- |
13 | 13 | */ |
@@ -94,14 +94,9 @@ replace_outer_var(PlannerInfo *root, Var *var) |
94 | 94 | * NOTE: in sufficiently complex querytrees, it is possible for the same |
95 | 95 | * varno/abslevel to refer to different RTEs in different parts of the |
96 | 96 | * parsetree, so that different fields might end up sharing the same Param |
97 | | - * number.As long as we check the vartype as well, I believe that this |
98 | | - * sort of aliasing will cause no trouble. The correct field should get |
99 | | - * stored into the Param slot at execution in each part of the tree. |
100 | | - * |
101 | | - * We also need to demand a match on vartypmod. This does not matter for |
102 | | - * the Param itself, since those are not typmod-dependent, but it does |
103 | | - * matter when make_subplan() instantiates a modified copy of the Var for |
104 | | - * a subplan's args list. |
| 97 | + * number.As long as we check the vartype/typmod as well, I believe that |
| 98 | + * this sort of aliasing will cause no trouble. The correct field should |
| 99 | + * get stored into the Param slot at execution in each part of the tree. |
105 | 100 | */ |
106 | 101 | i=0; |
107 | 102 | foreach(ppl,root->glob->paramlist) |
|