From f2689e421d7ca0a103e33f5b92bb0676c80e1d04 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sun, 17 Aug 2008 02:19:19 +0000 Subject: [PATCH] Remove prohibition against SubLinks in the WHERE clause of an EXISTS subquery that we're considering pulling up. I hadn't wanted to think through whether that could work during the first pass at this stuff. However, on closer inspection it seems to be safe enough. --- src/backend/optimizer/plan/subselect.c | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/src/backend/optimizer/plan/subselect.c b/src/backend/optimizer/plan/subselect.c index d4374516ac..9eaeaedc68 100644 --- a/src/backend/optimizer/plan/subselect.c +++ b/src/backend/optimizer/plan/subselect.c @@ -7,7 +7,7 @@ * Portions Copyright (c) 1994, Regents of the University of California * * IDENTIFICATION - * $PostgreSQL: pgsql/src/backend/optimizer/plan/subselect.c,v 1.134 2008/08/17 01:20:00 tgl Exp $ + * $PostgreSQL: pgsql/src/backend/optimizer/plan/subselect.c,v 1.135 2008/08/17 02:19:19 tgl Exp $ * *------------------------------------------------------------------------- */ @@ -969,14 +969,6 @@ convert_EXISTS_sublink_to_join(PlannerInfo *root, SubLink *sublink, if (contain_volatile_functions(whereClause)) return false; - /* - * Also disallow SubLinks within the WHERE clause. (XXX this could - * probably be supported, but it would complicate the transformation - * below, and it doesn't seem worth worrying about in a first pass.) - */ - if (contain_subplans(whereClause)) - return false; - /* * Prepare to pull up the sub-select into top range table. *