pgsql: Allow USING and INTO clauses of plpgsql's EXECUTE to appear in

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Allow USING and INTO clauses of plpgsql's EXECUTE to appear in
Date: 2010-08-19 18:57:57
Message-ID: 20100819185757.B809B7541D7@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Allow USING and INTO clauses of plpgsql's EXECUTE to appear in either order.

Aside from being more forgiving, this prevents a rather surprising misbehavior
when the "wrong" order was used: the old code didn't throw a syntax error,
but absorbed the INTO clause into the last USING expression, which then did
strange things downstream.

Intentionally not changing the documentation; we'll continue to advertise
only the "standard" clause order.

Backpatch to 8.4, where the USING clause was added to EXECUTE.

Modified Files:
--------------
pgsql/src/pl/plpgsql/src:
gram.y (r1.143 -> r1.144)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/gram.y?r1=1.143&r2=1.144)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2010-08-19 18:58:04 pgsql: Allow USING and INTO clauses of plpgsql's EXECUTE to appear in
Previous Message Tom Lane 2010-08-19 18:11:08 pgsql: Keep exec_simple_check_plan() from thinking "SELECT foo INTO bar"