aboutsummaryrefslogtreecommitdiff
path: root/src/backend/optimizer
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2007-10-04 20:45:17 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2007-10-04 20:45:17 +0000
commitd9e961d52737823b30549d5c130790d62a79731f (patch)
tree0e9aae2019168d1ce7add6d39ab0a0af80852f4b /src/backend/optimizer
parent45cd13c8ab05aef5a334bca8a2d1e9a1b9b8815e (diff)
downloadpostgresql-d9e961d52737823b30549d5c130790d62a79731f.tar.gz
postgresql-d9e961d52737823b30549d5c130790d62a79731f.zip
Keep the planner from failing on "WHERE false AND something IN (SELECT ...)".
eval_const_expressions simplifies this to just "WHERE false", but we have already done pull_up_IN_clauses so the IN join will be done, or at least planned, anyway. The trouble case comes when the sub-SELECT is itself a join and we decide to implement the IN by unique-ifying the sub-SELECT outputs: with no remaining reference to the output Vars in WHERE, we won't have propagated the Vars up to the upper join point, leading to "variable not found in subplan target lists" error. Fix by adding an extra scan of in_info_list and forcing all Vars mentioned therein to be propagated up to the IN join point. Per bug report from Miroslav Sulc.
Diffstat (limited to 'src/backend/optimizer')
-rw-r--r--src/backend/optimizer/plan/initsplan.c36
-rw-r--r--src/backend/optimizer/plan/planmain.c9
2 files changed, 43 insertions, 2 deletions
diff --git a/src/backend/optimizer/plan/initsplan.c b/src/backend/optimizer/plan/initsplan.c
index b1e69b7b3a5..25efaf59d7d 100644
--- a/src/backend/optimizer/plan/initsplan.c
+++ b/src/backend/optimizer/plan/initsplan.c
@@ -8,7 +8,7 @@
*
*
* IDENTIFICATION
- * $Header: /cvsroot/pgsql/src/backend/optimizer/plan/initsplan.c,v 1.91.2.3 2005/09/28 21:17:48 tgl Exp $
+ * $Header: /cvsroot/pgsql/src/backend/optimizer/plan/initsplan.c,v 1.91.2.4 2007/10/04 20:45:17 tgl Exp $
*
*-------------------------------------------------------------------------
*/
@@ -126,6 +126,40 @@ build_base_rel_tlists(Query *root, List *final_tlist)
}
/*
+ * add_IN_vars_to_tlists
+ * Add targetlist entries for each var needed in InClauseInfo entries
+ * to the appropriate base relations.
+ *
+ * Normally this is a waste of time because scanning of the WHERE clause
+ * will have added them. But it is possible that eval_const_expressions()
+ * simplified away all references to the vars after the InClauseInfos were
+ * made. We need the IN's righthand-side vars to be available at the join
+ * anyway, in case we try to unique-ify the subselect's outputs. (The only
+ * known case that provokes this is "WHERE false AND foo IN (SELECT ...)".
+ * We don't try to be very smart about such cases, just correct.)
+ */
+void
+add_IN_vars_to_tlists(Query *root)
+{
+ List *l;
+
+ foreach(l, root->in_info_list)
+ {
+ InClauseInfo *ininfo = (InClauseInfo *) lfirst(l);
+ List *in_vars;
+
+ in_vars = pull_var_clause((Node *) ininfo->sub_targetlist, false);
+ if (in_vars != NIL)
+ {
+ add_vars_to_targetlist(root, in_vars,
+ bms_union(ininfo->lefthand,
+ ininfo->righthand));
+ freeList(in_vars);
+ }
+ }
+}
+
+/*
* add_vars_to_targetlist
* For each variable appearing in the list, add it to the owning
* relation's targetlist if not already present, and mark the variable
diff --git a/src/backend/optimizer/plan/planmain.c b/src/backend/optimizer/plan/planmain.c
index a8159dd972b..94365808b84 100644
--- a/src/backend/optimizer/plan/planmain.c
+++ b/src/backend/optimizer/plan/planmain.c
@@ -14,7 +14,7 @@
*
*
* IDENTIFICATION
- * $Header: /cvsroot/pgsql/src/backend/optimizer/plan/planmain.c,v 1.78.4.1 2005/09/28 21:17:49 tgl Exp $
+ * $Header: /cvsroot/pgsql/src/backend/optimizer/plan/planmain.c,v 1.78.4.2 2007/10/04 20:45:17 tgl Exp $
*
*-------------------------------------------------------------------------
*/
@@ -136,6 +136,13 @@ query_planner(Query *root, List *tlist, double tuple_fraction,
(void) distribute_quals_to_rels(root, (Node *) root->jointree, false);
/*
+ * Vars mentioned in InClauseInfo items also have to be added to baserel
+ * targetlists. Nearly always, they'd have got there from the original
+ * WHERE qual, but in corner cases maybe not.
+ */
+ add_IN_vars_to_tlists(root);
+
+ /*
* Use the completed lists of equijoined keys to deduce any implied
* but unstated equalities (for example, A=B and B=C imply A=C).
*/