summaryrefslogtreecommitdiff
path: root/src/backend/optimizer/plan/setrefs.c
diff options
context:
space:
mode:
Diffstat (limited to 'src/backend/optimizer/plan/setrefs.c')
-rw-r--r--src/backend/optimizer/plan/setrefs.c10
1 files changed, 5 insertions, 5 deletions
diff --git a/src/backend/optimizer/plan/setrefs.c b/src/backend/optimizer/plan/setrefs.c
index 3585a703fbd..ec5552327fb 100644
--- a/src/backend/optimizer/plan/setrefs.c
+++ b/src/backend/optimizer/plan/setrefs.c
@@ -2289,11 +2289,11 @@ set_join_references(PlannerInfo *root, Join *join, int rtoffset)
* the outer-join level at which they are used, Vars seen in the
* NestLoopParam expression may have nullingrels that are just a
* subset of those in the Vars actually available from the outer
- * side. Another case that can cause that to happen is explained
- * in the comments for process_subquery_nestloop_params. Not
- * checking this exactly is a bit grotty, but the work needed to
- * make things match up perfectly seems well out of proportion to
- * the value.
+ * side. Lateral references can create the same situation, as
+ * explained in the comments for process_subquery_nestloop_params
+ * and paraminfo_get_equal_hashops. Not checking this exactly is
+ * a bit grotty, but the work needed to make things match up
+ * perfectly seems well out of proportion to the value.
*/
nlp->paramval = (Var *) fix_upper_expr(root,
(Node *) nlp->paramval,