> Per recent discussion[1], plpgsql returns fairly unhelpful "syntax > error" messages when a %TYPE or %ROWTYPE construct references a > nonexistent object. Here's a quick little finger exercise to try > to improve that.
Looks this modify the error message, I want to know how ould we treat error-message-compatible issue during minor / major upgrade.
There is no bug here so no back-patch; and we are not yet past feature freeze for v17.