Re: identifying unrecognized node type errors - Mailing list pgsql-hackers

From David Rowley
Subject Re: identifying unrecognized node type errors
Date
Msg-id CAApHDvqRz1ERNOtTxH6=LGfd=s4UOLa6ekEb+GUS4PZABk5OOQ@mail.gmail.com
Whole thread Raw
In response to identifying unrecognized node type errors  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Fri, 25 Mar 2022 at 08:53, Andrew Dunstan <andrew@dunslane.net> wrote:
> 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?

Can you not use \set VERBOSITY verbose ?

postgres=# \set VERBOSITY verbose
postgres=# select 1/0;
ERROR:  22012: division by zero
LOCATION:  int4div, int.c:846

David



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: identifying unrecognized node type errors
Next
From: Daniel Gustafsson
Date:
Subject: Re: Small TAP tests cleanup for Windows and unused modules