pgsql: Fix a few bogus statement type names in plpgsql error messages. - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Fix a few bogus statement type names in plpgsql error messages.
Date
Msg-id E1ZRqDd-0007C1-A0@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix a few bogus statement type names in plpgsql error messages.

plpgsql's error location context messages ("PL/pgSQL function fn-name line
line-no at stmt-type") would misreport a CONTINUE statement as being an
EXIT, and misreport a MOVE statement as being a FETCH.  These are clear
bugs that have been there a long time, so back-patch to all supported
branches.

In addition, in 9.5 and HEAD, change the description of EXECUTE from
"EXECUTE statement" to just plain EXECUTE; there seems no good reason why
this statement type should be described differently from others that have
a well-defined head keyword.  And distinguish GET STACKED DIAGNOSTICS from
plain GET DIAGNOSTICS.  These are a bit more of a judgment call, and also
affect existing regression-test outputs, so I did not back-patch into
stable branches.

Pavel Stehule and Tom Lane

Branch
------
REL9_3_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/8992e1acde19342f70210801b0442b6be68ef4f7

Modified Files
--------------
src/pl/plpgsql/src/pl_funcs.c |    4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Fix a few bogus statement type names in plpgsql error messages.
Next
From: Tom Lane
Date:
Subject: pgsql: Fix a few bogus statement type names in plpgsql error messages.