Re: unrecognized node type: 350

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: shashidhar Reddy <shashidharreddy001(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: unrecognized node type: 350
Date: 2022-11-16 18:52:15
Message-ID: 1384426.1668624735@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> st 16. 11. 2022 v 19:01 odesílatel shashidhar Reddy <
> shashidharreddy001(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Stehule 2022-11-17 03:13:24 Re: unrecognized node type: 350
Previous Message Pavel Stehule 2022-11-16 18:25:53 Re: unrecognized node type: 350