Re: ERROR: unrecognized node type
От | Adrian Klaver |
---|---|
Тема | Re: ERROR: unrecognized node type |
Дата | |
Msg-id | 80c95c0d-3d32-8fad-0533-d26ebc2e8e5e@aklaver.com обсуждение исходный текст |
Ответ на | Re: ERROR: unrecognized node type (Amine Tengilimoglu <aminetengilimoglu@gmail.com>) |
Ответы |
Re: ERROR: unrecognized node type
|
Список | pgsql-general |
On 9/29/21 10:54 AM, Amine Tengilimoglu wrote: > I thought that the server version can be guess from the screenshot . I Unless folks are using plain text only email readers. That is why screenshots are generally a bad idea for textual information. For the record the Postgres version is 12.8. > already update the latest minor pg version and it didn't work :) You will need to update with the actual minor version. When you do the pg_dump, what is the error message? > > 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 >> > -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: