Keep exec_simple_check_plan() from thinking "SELECT foo INTO bar" is simple.
authorTom Lane <[email protected]>
Thu, 19 Aug 2010 18:11:02 +0000 (18:11 +0000)
committerTom Lane <[email protected]>
Thu, 19 Aug 2010 18:11:02 +0000 (18:11 +0000)
It's not clear if this situation can occur in plpgsql other than via the
EXECUTE USING case Heikki illustrated, which I will shortly close off.
However, ignoring the intoClause if it's there is surely wrong, so let's
patch it for safety.

Backpatch to 8.3, which is as far back as this code has a PlannedStmt
to deal with.  There might be another way to make an equivalent test
before that, but since this is just preventing hypothetical bugs,
I'm not going to obsess about it.

src/pl/plpgsql/src/pl_exec.c

index 04067c176ea3083c5150dcb2fe37477201bc500d..8d0c62559b6344506948e3e726a07982a5983e84 100644 (file)
@@ -8,7 +8,7 @@
  *
  *
  * IDENTIFICATION
- *       $PostgreSQL: pgsql/src/pl/plpgsql/src/pl_exec.c,v 1.244.2.9 2010/08/19 17:31:56 tgl Exp $
+ *       $PostgreSQL: pgsql/src/pl/plpgsql/src/pl_exec.c,v 1.244.2.10 2010/08/19 18:11:02 tgl Exp $
  *
  *-------------------------------------------------------------------------
  */
@@ -5148,6 +5148,8 @@ exec_simple_check_plan(PLpgSQL_expr *expr)
         */
        if (!IsA(stmt, PlannedStmt))
                return;
+       if (stmt->commandType != CMD_SELECT || stmt->intoClause)
+               return;
        plan = stmt->planTree;
        if (!IsA(plan, Result))
                return;