public inbox for [email protected]
help / color / mirror / Atom feed(PostgreSQL 17) View usage resulting in 'ERROR: unrecognized node type: 2'
2+ messages / 2 participants
[nested] [flat]
* (PostgreSQL 17) View usage resulting in 'ERROR: unrecognized node type: 2'
@ 2026-03-12 21:02 Martin Goodson <[email protected]>
2026-03-13 02:22 ` Re: (PostgreSQL 17) View usage resulting in 'ERROR: unrecognized node type: 2' Tom Lane <[email protected]>
0 siblings, 1 reply; 2+ messages in thread
From: Martin Goodson @ 2026-03-12 21:02 UTC (permalink / raw)
To: pgsql-generallists.postgresql.org <[email protected]>
I don't know if anyone has seen this, maybe it's a very common error
I've just never come across before, but I'm encountering the following
problem:
I've exported some views from a PG14 database and loaded them into a
brand new PG17 database via a plain text format pg_dump.
No errors were reported during the dump, so no problems creating the
views reported.
However, attempting to query the views - which are pretty complex, to be
fair - result in the query erroring immediately with 'ERROR:
unrecognized node type: 2'
I've tried repeating the load from the pg_dump file, and it still errors
immediately with the same error message.
I've tried creating a copy of one of the views (extracting the view
definition with pg_get_viewdef, and wrapping a create view around it)
... that results in a new view that is created successfully, but which
still results in an immediate 'ERROR: unrecognized node type: 2' when
you query the view.
Unfortunately I cannot provide the view definition due to
confidentiality agreements 🙁
Any suggestions to what might be the underlying cause for this? Has this
happened anywhere else? Is there some manner of issue with complexity in
views in PG17?
Any suggestions, or further information, would be very gratefully
received 🙂
Thank you.
--
--
Martin Goodson.
"Have you thought up some clever plan, Doctor?"
"Yes, Jamie, I believe I have."
"What're you going to do?"
"Bung a rock at it."
--
--
Martin Goodson.
"Have you thought up some clever plan, Doctor?"
"Yes, Jamie, I believe I have."
"What're you going to do?"
"Bung a rock at it."
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: (PostgreSQL 17) View usage resulting in 'ERROR: unrecognized node type: 2'
2026-03-12 21:02 (PostgreSQL 17) View usage resulting in 'ERROR: unrecognized node type: 2' Martin Goodson <[email protected]>
@ 2026-03-13 02:22 ` Tom Lane <[email protected]>
0 siblings, 0 replies; 2+ messages in thread
From: Tom Lane @ 2026-03-13 02:22 UTC (permalink / raw)
To: Martin Goodson <[email protected]>; +Cc: pgsql-generallists.postgresql.org <[email protected]>
Martin Goodson <[email protected]> writes:
> I've exported some views from a PG14 database and loaded them into a
> brand new PG17 database via a plain text format pg_dump.
> No errors were reported during the dump, so no problems creating the
> views reported.
> However, attempting to query the views - which are pretty complex, to be
> fair - result in the query erroring immediately with 'ERROR:
> unrecognized node type: 2'
That is certainly a bug, but there's zero hope of anyone fixing it
without a reproducible test case to poke at.
Looking at our commit log, there was a fix in 17.3 for a problem that
resulted in "unrecognized node type" errors [1], so it'd behoove you to
make sure you are running 17.recent before spending any more effort.
regards, tom lane
[1] https://www.postgresql.org/message-id/flat/18778-24cd399df6c806af%40postgresql.org
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2026-03-13 02:22 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-03-12 21:02 (PostgreSQL 17) View usage resulting in 'ERROR: unrecognized node type: 2' Martin Goodson <[email protected]>
2026-03-13 02:22 ` Tom Lane <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox