| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: identifying unrecognized node type errors |
| Date: | 2022-03-24 20:01:07 |
| Message-ID: | CAApHDvqRz1ERNOtTxH6=LGfd=s4UOLa6ekEb+GUS4PZABk5OOQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 25 Mar 2022 at 08:53, Andrew Dunstan <andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2022-03-24 20:02:09 | Re: Small TAP tests cleanup for Windows and unused modules |
| Previous Message | Andrew Dunstan | 2022-03-24 19:53:42 | identifying unrecognized node type errors |