| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Amine Tengilimoglu <aminetengilimoglu(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: ERROR: unrecognized node type |
| Date: | 2021-09-29 18:37:16 |
| Message-ID: | 2994270.1632940636@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
> Unless folks are using plain text only email readers. That is why
> screenshots are generally a bad idea for textual information. For the
> record the Postgres version is 12.8.
Hmm, if it's v12 then NodeTag 223 is T_List, which is ... a bit
surprising. That's a common enough node type that "oversight"
doesn't seem to fly as an explanation.
I don't think we'll be able to make progress on this without a
lot more detail. A self-contained example that triggers it
would be very useful; or maybe you could get a backtrace from
the point of the error?
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2021-09-29 21:10:06 | Re: ERROR: unrecognized node type |
| Previous Message | Tom Lane | 2021-09-29 18:17:44 | Re: ERROR: unrecognized node type |