Re: unrecognized node type: 350
От | Tom Lane |
---|---|
Тема | Re: unrecognized node type: 350 |
Дата | |
Msg-id | 1384426.1668624735@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: unrecognized node type: 350 (Pavel Stehule <pavel.stehule@gmail.com>) |
Ответы |
Re: unrecognized node type: 350
|
Список | pgsql-general |
Pavel Stehule <pavel.stehule@gmail.com> writes: > st 16. 11. 2022 v 19:01 odesílatel shashidhar Reddy < > shashidharreddy001@gmail.com> napsal: >>> 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] > The extension plpgsql_check does not contain this message. Well, no --- it's the kernel reporting a segfault in plpgsql_check. Although now that you mention it, there should also be traces of this crash in the Postgres log; it would be interesting to see what's reported there. > Node with number 350 should be ParamRef This is v13, so if I wrangled gdb correctly 350 is FuncCall. (One thing I'm wondering though is if the extension somehow got compiled against wrong-version headers. But you'd expect that it largely wouldn't work at all if so.) regards, tom lane
В списке pgsql-general по дате отправления: