aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeFunctionscan.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2015-08-18 19:22:38 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2015-08-18 19:22:38 -0400
commit17aa3c2d13a050a264bd3fee954ae98c0ae14ecf (patch)
tree1e1eb669c427cee884530bbab41c1102ff915f10 /src/backend/executor/nodeFunctionscan.c
parent138f76533cdcbf4b6c61ba9f8d92dd74b332ccba (diff)
downloadpostgresql-17aa3c2d13a050a264bd3fee954ae98c0ae14ecf.tar.gz
postgresql-17aa3c2d13a050a264bd3fee954ae98c0ae14ecf.zip
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/executor/nodeFunctionscan.c')
0 files changed, 0 insertions, 0 deletions