(PostgreSQL 17) View usage resulting in 'ERROR: unrecognized node type: 2'

Martin Goodson <kaemaril@googlemail.com>

From: Martin Goodson <kaemaril@googlemail.com>
To: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Date: 2026-03-12T21:02:59Z
Lists: pgsql-general
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."