-
- Downloads
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
Showing
- src/pl/plpgsql/src/pl_funcs.c 5 additions, 4 deletionssrc/pl/plpgsql/src/pl_funcs.c
- src/test/regress/expected/event_trigger.out 17 additions, 17 deletionssrc/test/regress/expected/event_trigger.out
- src/test/regress/expected/plpgsql.out 6 additions, 6 deletionssrc/test/regress/expected/plpgsql.out
- src/test/regress/expected/triggers.out 5 additions, 5 deletionssrc/test/regress/expected/triggers.out
Loading
Please register or sign in to comment