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.
gram.y (r1.125 -> r184.108.40.206)
pgsql-committers by date
|Next:||From: Tom Lane||Date: 2010-08-19 22:55:01|
|Subject: pgsql: Bring some sanity to the trace_recovery_messages code and docs.|
|Previous:||From: Tom Lane||Date: 2010-08-19 18:58:04|
|Subject: pgsql: Allow USING and INTO clauses of plpgsql's EXECUTE to appear in |