]> granicus.if.org Git - postgresql/commit
Allow USING and INTO clauses of plpgsql's EXECUTE to appear in either order.
authorTom Lane <tgl@sss.pgh.pa.us>
Thu, 19 Aug 2010 18:58:11 +0000 (18:58 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Thu, 19 Aug 2010 18:58:11 +0000 (18:58 +0000)
commitaffcd50e4090a420fb235b11af007ca3f9ccf967
treee1f6543fc8dc3b9b703ee3a861033543d7c34047
parenta1bde80db45fe9f123abb2a493b9dfcb755d427d
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.
src/pl/plpgsql/src/gram.y