Re: identifying unrecognized node type errors

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:10:39
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)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

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2022-03-24 20:20:50 Re: make MaxBackends available in _PG_init
Previous Message Pavel Borisov 2022-03-24 20:02:55 Re: XID formatting and SLRU refactorings (was: Add 64-bit XIDs into PostgreSQL 15)