From: Tom Lane <tgl@sss.pgh.pa.us>
To: Martin Goodson <kaemaril@googlemail.com>
cc: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Subject: Re: (PostgreSQL 17) View usage resulting in 'ERROR: unrecognized node type: 2'
In-reply-to: <d1c8f728-6573-4e79-b7bf-aabba0f53ccd@googlemail.com>
References: <d1c8f728-6573-4e79-b7bf-aabba0f53ccd@googlemail.com>
Comments: In-reply-to Martin Goodson <kaemaril@googlemail.com>
	message dated "Thu, 12 Mar 2026 21:02:59 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4798.1773368569.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 12 Mar 2026 22:22:49 -0400
Message-ID: <4799.1773368569@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/4799.1773368569%40sss.pgh.pa.us>
Precedence: bulk

Martin Goodson <kaemaril@googlemail.com> 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%40po=
stgresql.org