On 3/24/22 16:10, Tom Lane wrote:
> Andrew Dunstan <andrew@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.
>
>
Yeah, must have had some brain fade. Sorry for the noise.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com