aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/arrayfuncs.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2010-08-19 18:57:57 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2010-08-19 18:57:57 +0000
commit9676b01028139ca399f2564f6c4cb40fffe2ec07 (patch)
treeebdffe0331988a5dc8d37ed71de99e8de0a94113 /src/backend/utils/adt/arrayfuncs.c
parentf4b4a46f01eca60f4e7a2827cf13ef8bbff5f1f8 (diff)
downloadpostgresql-9676b01028139ca399f2564f6c4cb40fffe2ec07.tar.gz
postgresql-9676b01028139ca399f2564f6c4cb40fffe2ec07.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/arrayfuncs.c')
0 files changed, 0 insertions, 0 deletions