diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2010-08-19 18:58:11 +0000 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2010-08-19 18:58:11 +0000 |
commit | affcd50e4090a420fb235b11af007ca3f9ccf967 (patch) | |
tree | e1f6543fc8dc3b9b703ee3a861033543d7c34047 /src/backend/utils/adt/arrayutils.c | |
parent | a1bde80db45fe9f123abb2a493b9dfcb755d427d (diff) | |
download | postgresql-affcd50e4090a420fb235b11af007ca3f9ccf967.tar.gz postgresql-affcd50e4090a420fb235b11af007ca3f9ccf967.zip |
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.
Diffstat (limited to 'src/backend/utils/adt/arrayutils.c')
0 files changed, 0 insertions, 0 deletions