]> 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:57:57 +0000 (18:57 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Thu, 19 Aug 2010 18:57:57 +0000 (18:57 +0000)
commit9676b01028139ca399f2564f6c4cb40fffe2ec07
treeebdffe0331988a5dc8d37ed71de99e8de0a94113
parentf4b4a46f01eca60f4e7a2827cf13ef8bbff5f1f8
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