| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: identifying unrecognized node type errors |
| Date: | 2022-03-24 20:34:35 |
| Message-ID: | 2824e64d-4e2a-ac89-67ec-b8a80e3053ec@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/24/22 16:10, Tom Lane wrote:
> 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.
>
>
Yeah, must have had some brain fade. Sorry for the noise.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2022-03-24 20:40:11 | Re: Doc patch: replace 'salesmen' with 'salespeople' |
| Previous Message | Tom Lane | 2022-03-24 20:34:13 | Re: [PATCH] pg_statio_all_tables: several rows per table due to invalid TOAST index |