unrecognized node type: 350

Any help on this?

On Wed, 16 Nov, 2022, 1:53 pm shashidhar Reddy, <
shashidharreddy001@gmail.com> wrote:

On 16 Nov 2022, at 09:23, shashidhar Reddy <shashidharreddy001@gmail.com> wrote:

We have upgraded postgresql from version 12 to 13.8 and after that facing unrecognized node type: 350, what could be the issue?
2022-11-16 02:28:08,957 DEBUG Logger#insert - 2022-11-16-02:28:08 - ERROR - 2022-11-16-02:28:08 - org.postgresql.util.PSQLException: ERROR: unrecognized node type: 350

Are you running a version of JDBC which supports postgres 13?

--
Daniel Gustafsson https://vmware.com/

We are using 42.2.21 jdbc version

On Wed, 16 Nov, 2022, 6:26 pm Daniel Gustafsson, <daniel@yesql.se> wrote:

shashidhar Reddy <shashidharreddy001@gmail.com> writes:

We have upgraded postgresql from version 12 to 13.8 and after that
facing unrecognized
node type: 350, what could be the issue?

What is the query that produces that? Do you have any extensions
loaded in the server (auto_explain or the like)?

regards, tom lane

Tom,

We have extensions like plpgsql_check and plprofiler. Below is the query
log with errors

2022-11-16 02:28:08,957 DEBUG Logger#insert - 2022-11-16-02:28:08 - ERROR -
2022-11-16-02:28:08 - org.postgresql.util.PSQLException: ERROR:
unrecognized node type: 350
Where: PL/pgSQL function
ccmiexceptions.computetariffexceptions(integer,integer,integer,integer[])
line 9 at IF
SQL statement "SELECT CCMIExceptions.ComputeTariffExceptions($1, $2, $3,
$4);"
PL/pgSQL function serviceexceptions.recomputeexception(character
varying,integer,integer,integer,integer,integer[]) line 7 at EXECUTE
SQL statement "SELECT
ServiceExceptions.RecomputeException(exceptionRecord.rule,
exceptionRecord.exceptionId, exceptionRecord.columnId,
exceptionRecord.serviceTypeId, invoiceIdX, billIdsX)"
PL/pgSQL function
serviceexceptions.recomputeexceptions(integer,integer[],integer,integer[])
line 23 at PERFORM
SQL statement "SELECT ServiceExceptions.RecomputeExceptions(invoiceIdX,
NULL, serviceTypeIdX, categoryIdsX)"
PL/pgSQL function
serviceexceptions.recomputeinvoice(integer,integer,integer[]) line 3 at
PERFORM[ERROR: unrecognized node type: 350
Where: PL/pgSQL function
ccmiexceptions.computetariffexceptions(integer,integer,integer,integer[])
line 9 at IF
SQL statement "SELECT CCMIExceptions.ComputeTariffExceptions($1, $2, $3,
$4);"
PL/pgSQL function serviceexceptions.recomputeexception(character
varying,integer,integer,integer,integer,integer[]) line 7 at EXECUTE
SQL statement "SELECT
ServiceExceptions.RecomputeException(exceptionRecord.rule,
exceptionRecord.exceptionId, exceptionRecord.columnId,
exceptionRecord.serviceTypeId, invoiceIdX, billIdsX)"
PL/pgSQL function
serviceexceptions.recomputeexceptions(integer,integer[],integer,integer[])
line 23 at PERFORM
SQL statement "SELECT ServiceExceptions.RecomputeExceptions(invoiceIdX,
NULL, serviceTypeIdX, categoryIdsX)"
PL/pgSQL function
serviceexceptions.recomputeinvoice(integer,integer,integer[]) line 3 at
PERFORM] (test-import-configuration - simple-pdf-splitflag.xml)
2022-11-16 02:28:08,965 ERROR XmlImport#processInvoice - ERROR:
unrecognized node type: 350

On Wed, Nov 16, 2022 at 7:57 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:

shashidhar Reddy <shashidharreddy001@gmail.com> writes:

We have upgraded postgresql from version 12 to 13.8 and after that
facing unrecognized
node type: 350, what could be the issue?

What is the query that produces that? Do you have any extensions
loaded in the server (auto_explain or the like)?

regards, tom lane

--
Shashidhar

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

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:

I have upgraded them to latest version.

By "update" I meant "bug fix". Some bit of code within the server
is failing to cope with a data structure it needs to cope with.
But you need to identify what bit of code that is before you'll
have any basis for filing a bug report.

regards, tom lane

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

shashidhar Reddy <shashidharreddy001@gmail.com> writes:

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]

That would certainly suggest a problem in plpgsql_check.
It might or might not be related to the node-type error.

regards, tom lane

Extension version is 2.2. Is anything need to be done? To fix this issue?

On Wed, 16 Nov, 2022, 10:06 pm Tom Lane, <tgl@sss.pgh.pa.us> wrote:

shashidhar Reddy <shashidharreddy001@gmail.com> writes:

Extension version is 2.2. Is anything need to be done? To fix this issue?

You could start by getting the information I asked for, ie where is
this error being thrown from according to log_error_verbosity=verbose.

regards, tom lane

Hi

st 16. 11. 2022 v 19:01 odesílatel shashidhar Reddy <
shashidharreddy001@gmail.com> napsal:

Extension version is 2.2. Is anything need to be done? To fix this issue?

On Wed, 16 Nov, 2022, 10:06 pm Tom Lane, <tgl@sss.pgh.pa.us> wrote:

shashidhar Reddy <shashidharreddy001@gmail.com> writes:

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]

That would certainly suggest a problem in plpgsql_check.
It might or might not be related to the node-type error.

The extension plpgsql_check does not contain this message. More in typical
usage, the plpgsql_check is not active at runtime (but it depends on usage).

Node with number 350 should be ParamRef

Can you show source code of functions that fail? Can you show plpgsql_check
configuration?

Regards

Pavel

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

st 16. 11. 2022 v 19:52 odesílatel Tom Lane <tgl@sss.pgh.pa.us> napsal:

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.

plpgsql_check can be used as a profiler or tracer too. But this
functionality is not enabled by default.

So usually at runtime, the plpgsql_check is not active. So it can be nice
to get plpgsql_check configuration and stack trace.

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.)

I did error in calculation, it is FuncCall

Regards

Pavel

Pavel,

Plpgsql_check configured under postures 13 lib.

If it us not enabled default how can I do it?

On Thu, 17 Nov, 2022, 8:44 am Pavel Stehule, <pavel.stehule@gmail.com>
wrote:

čt 17. 11. 2022 v 6:18 odesílatel shashidhar Reddy <
shashidharreddy001@gmail.com> napsal:

Pavel,

Plpgsql_check configured under postures 13 lib.

If it us not enabled default how can I do it?

Do you use profiler or tracer or passive mode from plpgsql_check?

What is result of "show plpgsql_check.mode" ?

Show plpgsql_check.mode gives an error as unrecognized configuration
parameter.

We use plprofiler

On Thu, 17 Nov, 2022, 10:55 am Pavel Stehule, <pavel.stehule@gmail.com>
wrote:

čt 17. 11. 2022 v 6:55 odesílatel shashidhar Reddy <
shashidharreddy001@gmail.com> napsal:

Show plpgsql_check.mode gives an error as unrecognized configuration
parameter.

We use plprofiler

it can be plprofiler issue, or maybe some problem when plpgsql_check is
used with plprofiler together

can you execute following scenarios

1. uninstall plpgsql_check and check if you can get the exception

2. install plpgsql_check and uninstall plprofiler, and check the issue

3. try to install debug symbols and send to us stack trace.

Regards

Pavel