Tom Lane 4c3754ffe0 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		2015-08-18 19:22:37 -04:00
..
src	Fix a few bogus statement type names in plpgsql error messages.	2015-08-18 19:22:37 -04:00
Makefile	Make init-po and update-po recursive make targets	2012-06-29 14:01:54 +03:00