diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2015-08-18 19:22:38 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2015-08-18 19:22:38 -0400 |
commit | fb41bf4b5169015169f41ed0a0d4f8ad1d823973 (patch) | |
tree | 5f7a0957b059d2f84b9e9268b14ada88c20c1758 /src/backend/access/gin/ginfast.c | |
parent | ed51165907e5b413cf221bd82c7f4274bf6ab58f (diff) |
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
Diffstat (limited to 'src/backend/access/gin/ginfast.c')
0 files changed, 0 insertions, 0 deletions