Re: ERROR: unrecognized node type - Mailing list pgsql-general

From Amine Tengilimoglu
Subject Re: ERROR: unrecognized node type
Date
Msg-id CADTdw-xJX90ToHcrMxxWvJWssjvbBVunq-W=EfXXu7is7+YobQ@mail.gmail.com
Whole thread Raw
In response to Re: ERROR: unrecognized node type  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ERROR: unrecognized node type  (Adrian Klaver <adrian.klaver@aklaver.com>)
Re: ERROR: unrecognized node type  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
I thought that the server version can be guess from the screenshot . I already update the latest minor pg version and it didn't work :) 

   Thank you Tom. 

Tom Lane <tgl@sss.pgh.pa.us>, 29 Eyl 2021 Çar, 20:16 tarihinde şunu yazdı:
Amine Tengilimoglu <aminetengilimoglu@gmail.com> writes:
>   I am getting  the "ERROR:  unrecognized node type: 223" when I execute \d
> combinations in psql and even when getting backup with pg_dump... probably
> the same error will occur with other commands.  What is causing this issue,
> any idea? How to fix it?

You're not going to get any useful responses to that without more
details (at minimum, the server version).  However, a reasonable
bet is that some stored view or expression contains a parse node
that some part of the server code is failing to cope with.  We've
had such bugs in the past, but I don't know of any that are live
right now ... so maybe your answer is just "update to current
minor release".

If that doesn't help, it'd be good to try to isolate which database
object contains the problem, and then reconstruct what its definition
was, so we can try to understand where the oversight is.

                        regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: ERROR: unrecognized node type
Next
From: Adrian Klaver
Date:
Subject: Re: ERROR: unrecognized node type