From: | Amine Tengilimoglu <aminetengilimoglu(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "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 17:54:11 |
Message-ID: | CADTdw-xJX90ToHcrMxxWvJWssjvbBVunq-W=EfXXu7is7+YobQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)sss(dot)pgh(dot)pa(dot)us>, 29 Eyl 2021 Çar, 20:16 tarihinde şunu yazdı:
> Amine Tengilimoglu <aminetengilimoglu(at)gmail(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2021-09-29 18:10:53 | Re: ERROR: unrecognized node type |
Previous Message | Tom Lane | 2021-09-29 17:16:43 | Re: ERROR: unrecognized node type |