Andrew Dunstan <and...@dunslane.net> writes:
> As I was tracking down some of these errors in the sql/json patches I
> noticed that we have a whole lot of them in the code, so working out
> which one has triggered an error is not as easy as it might be. ISTM we
> could usefully prefix each such message with the name of the function in
> which it occurs, along the lines of this fragment for nodeFuncs.c. Thoughts?
-1. You're reinventing the error location support that already exists
inside elog. Just turn up log_error_verbosity instead.
regards, tom lane
