| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | identifying unrecognized node type errors |
| Date: | 2022-03-24 19:53:42 |
| Message-ID: | 41a2d88e-a3f2-2898-f922-98c3ee049c15@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| unknown-node-error-identifiers.patch | text/x-patch | 1.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2022-03-24 20:01:07 | Re: identifying unrecognized node type errors |
| Previous Message | Mark Dilger | 2022-03-24 19:50:42 | Re: Granting SET and ALTER SYSTE privileges for GUCs |