Re: unrecognized node type: 350
| От | shashidhar Reddy |
|---|---|
| Тема | Re: unrecognized node type: 350 |
| Дата | |
| Msg-id | CAH=zU4sLdFZNTHOeq7ixGV0nBB5W9bTa71aSF6qB28VgNw-rSw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: unrecognized node type: 350 (shashidhar Reddy <shashidharreddy001@gmail.com>) |
| Ответы |
Re: unrecognized node type: 350
|
| Список | pgsql-general |
I could see an error in syslogs, I am not sure what it means.
kernel: [93631.415790] postgres[86383]: segfault at 80 ip 00007f07f3e3eefd sp 00007fffcf1db500 error 4 in plpgsql_check.so[7f07f3e2e000+34000]
On Wed, Nov 16, 2022 at 9:36 PM shashidhar Reddy <shashidharreddy001@gmail.com> wrote:
Tom,I have upgraded them to latest version.I also used pg_upgrade check before upgrading the postures from 12 to 13.On Wed, 16 Nov, 2022, 9:32 pm Tom Lane, <tgl@sss.pgh.pa.us> wrote:shashidhar Reddy <shashidharreddy001@gmail.com> writes:
> We have extensions like plpgsql_check and plprofiler.
Hmm. My bet is that one of those needs an update. You could
probably narrow things down by setting log_error_verbosity to
"verbose" so that an error location shows in the postmaster log.
regards, tom lane
Shashidhar
В списке pgsql-general по дате отправления: