pg.ddx.io pgsql-general@postgresql.org mailing list archive
help / color / mirror / Atom feedunrecognized node type: 350
25+ messages / 4 participants
[nested] [flat]
* unrecognized node type: 350
@ 2022-11-16 08:23 shashidhar Reddy <shashidharreddy001@gmail.com>
0 siblings, 3 replies; 25+ messages in thread
From: shashidhar Reddy @ 2022-11-16 08:23 UTC (permalink / raw)
To: pgsql-general
Hello,
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
--
Shashidhar
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-16 11:48 shashidhar Reddy <shashidharreddy001@gmail.com>
parent: shashidhar Reddy <shashidharreddy001@gmail.com>
2 siblings, 0 replies; 25+ messages in thread
From: shashidhar Reddy @ 2022-11-16 11:48 UTC (permalink / raw)
To: pgsql-general
Any help on this?
On Wed, 16 Nov, 2022, 1:53 pm shashidhar Reddy, <
shashidharreddy001@gmail.com> wrote:
> Hello,
>
> 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
>
> --
> Shashidhar
>
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-16 12:56 Daniel Gustafsson <daniel@yesql.se>
parent: shashidhar Reddy <shashidharreddy001@gmail.com>
2 siblings, 1 reply; 25+ messages in thread
From: Daniel Gustafsson @ 2022-11-16 12:56 UTC (permalink / raw)
To: shashidhar Reddy <shashidharreddy001@gmail.com>; +Cc: pgsql-general
> 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/
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-16 13:48 shashidhar Reddy <shashidharreddy001@gmail.com>
parent: Daniel Gustafsson <daniel@yesql.se>
0 siblings, 0 replies; 25+ messages in thread
From: shashidhar Reddy @ 2022-11-16 13:48 UTC (permalink / raw)
To: daniel@yesql.se; +Cc: pgsql-general
We are using 42.2.21 jdbc version
On Wed, 16 Nov, 2022, 6:26 pm Daniel Gustafsson, <daniel@yesql.se> 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/
>
>
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-16 14:27 Tom Lane <tgl@sss.pgh.pa.us>
parent: shashidhar Reddy <shashidharreddy001@gmail.com>
2 siblings, 1 reply; 25+ messages in thread
From: Tom Lane @ 2022-11-16 14:27 UTC (permalink / raw)
To: shashidhar Reddy <shashidharreddy001@gmail.com>; +Cc: pgsql-general
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
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-16 15:55 shashidhar Reddy <shashidharreddy001@gmail.com>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 25+ messages in thread
From: shashidhar Reddy @ 2022-11-16 15:55 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-general
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
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-16 16:02 Tom Lane <tgl@sss.pgh.pa.us>
parent: shashidhar Reddy <shashidharreddy001@gmail.com>
0 siblings, 1 reply; 25+ messages in thread
From: Tom Lane @ 2022-11-16 16:02 UTC (permalink / raw)
To: shashidhar Reddy <shashidharreddy001@gmail.com>; +Cc: pgsql-general
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
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-16 16:06 shashidhar Reddy <shashidharreddy001@gmail.com>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 2 replies; 25+ messages in thread
From: shashidhar Reddy @ 2022-11-16 16:06 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-general
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
>
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-16 16:18 Tom Lane <tgl@sss.pgh.pa.us>
parent: shashidhar Reddy <shashidharreddy001@gmail.com>
1 sibling, 0 replies; 25+ messages in thread
From: Tom Lane @ 2022-11-16 16:18 UTC (permalink / raw)
To: shashidhar Reddy <shashidharreddy001@gmail.com>; +Cc: pgsql-general
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
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-16 16:33 shashidhar Reddy <shashidharreddy001@gmail.com>
parent: shashidhar Reddy <shashidharreddy001@gmail.com>
1 sibling, 1 reply; 25+ messages in thread
From: shashidhar Reddy @ 2022-11-16 16:33 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: 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
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-16 16:36 Tom Lane <tgl@sss.pgh.pa.us>
parent: shashidhar Reddy <shashidharreddy001@gmail.com>
0 siblings, 1 reply; 25+ messages in thread
From: Tom Lane @ 2022-11-16 16:36 UTC (permalink / raw)
To: shashidhar Reddy <shashidharreddy001@gmail.com>; +Cc: pgsql-general
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
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-16 18:01 shashidhar Reddy <shashidharreddy001@gmail.com>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 2 replies; 25+ messages in thread
From: shashidhar Reddy @ 2022-11-16 18:01 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-general
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.
>
> regards, tom lane
>
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-16 18:21 Tom Lane <tgl@sss.pgh.pa.us>
parent: shashidhar Reddy <shashidharreddy001@gmail.com>
1 sibling, 0 replies; 25+ messages in thread
From: Tom Lane @ 2022-11-16 18:21 UTC (permalink / raw)
To: shashidhar Reddy <shashidharreddy001@gmail.com>; +Cc: pgsql-general
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
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-16 18:25 Pavel Stehule <pavel.stehule@gmail.com>
parent: shashidhar Reddy <shashidharreddy001@gmail.com>
1 sibling, 1 reply; 25+ messages in thread
From: Pavel Stehule @ 2022-11-16 18:25 UTC (permalink / raw)
To: shashidhar Reddy <shashidharreddy001@gmail.com>; +Cc: Tom Lane <tgl@sss.pgh.pa.us>; pgsql-general
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
>> regards, tom lane
>>
>
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-16 18:52 Tom Lane <tgl@sss.pgh.pa.us>
parent: Pavel Stehule <pavel.stehule@gmail.com>
0 siblings, 1 reply; 25+ messages in thread
From: Tom Lane @ 2022-11-16 18:52 UTC (permalink / raw)
To: Pavel Stehule <pavel.stehule@gmail.com>; +Cc: shashidhar Reddy <shashidharreddy001@gmail.com>; 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
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-17 03:13 Pavel Stehule <pavel.stehule@gmail.com>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 25+ messages in thread
From: Pavel Stehule @ 2022-11-17 03:13 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: shashidhar Reddy <shashidharreddy001@gmail.com>; pgsql-general
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
>
> regards, tom lane
>
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-17 05:18 shashidhar Reddy <shashidharreddy001@gmail.com>
parent: Pavel Stehule <pavel.stehule@gmail.com>
0 siblings, 1 reply; 25+ messages in thread
From: shashidhar Reddy @ 2022-11-17 05:18 UTC (permalink / raw)
To: Pavel Stehule <pavel.stehule@gmail.com>; +Cc: Tom Lane <tgl@sss.pgh.pa.us>; pgsql-general
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:
>
>
> 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
>
>
>>
>> regards, tom lane
>>
>
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-17 05:24 Pavel Stehule <pavel.stehule@gmail.com>
parent: shashidhar Reddy <shashidharreddy001@gmail.com>
0 siblings, 1 reply; 25+ messages in thread
From: Pavel Stehule @ 2022-11-17 05:24 UTC (permalink / raw)
To: shashidhar Reddy <shashidharreddy001@gmail.com>; +Cc: Tom Lane <tgl@sss.pgh.pa.us>; pgsql-general
č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" ?
> On Thu, 17 Nov, 2022, 8:44 am Pavel Stehule, <pavel.stehule@gmail.com>
> wrote:
>
>>
>>
>> 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
>>
>>
>>>
>>> regards, tom lane
>>>
>>
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-17 05:55 shashidhar Reddy <shashidharreddy001@gmail.com>
parent: Pavel Stehule <pavel.stehule@gmail.com>
0 siblings, 1 reply; 25+ messages in thread
From: shashidhar Reddy @ 2022-11-17 05:55 UTC (permalink / raw)
To: Pavel Stehule <pavel.stehule@gmail.com>; +Cc: Tom Lane <tgl@sss.pgh.pa.us>; pgsql-general
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: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" ?
>
>
>
>
>> On Thu, 17 Nov, 2022, 8:44 am Pavel Stehule, <pavel.stehule@gmail.com>
>> wrote:
>>
>>>
>>>
>>> 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
>>>
>>>
>>>>
>>>> regards, tom lane
>>>>
>>>
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-17 06:04 Pavel Stehule <pavel.stehule@gmail.com>
parent: shashidhar Reddy <shashidharreddy001@gmail.com>
0 siblings, 1 reply; 25+ messages in thread
From: Pavel Stehule @ 2022-11-17 06:04 UTC (permalink / raw)
To: shashidhar Reddy <shashidharreddy001@gmail.com>; +Cc: Tom Lane <tgl@sss.pgh.pa.us>; pgsql-general
č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
>
> On Thu, 17 Nov, 2022, 10:55 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" ?
>>
>>
>>
>>
>>> On Thu, 17 Nov, 2022, 8:44 am Pavel Stehule, <pavel.stehule@gmail.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> 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
>>>>
>>>>
>>>>>
>>>>> regards, tom lane
>>>>>
>>>>
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-17 06:22 shashidhar Reddy <shashidharreddy001@gmail.com>
parent: Pavel Stehule <pavel.stehule@gmail.com>
0 siblings, 1 reply; 25+ messages in thread
From: shashidhar Reddy @ 2022-11-17 06:22 UTC (permalink / raw)
To: Pavel Stehule <pavel.stehule@gmail.com>; +Cc: Tom Lane <tgl@sss.pgh.pa.us>; pgsql-general
Ok, I will check.
On Thu, 17 Nov, 2022, 11:35 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
>
>
>>
>> On Thu, 17 Nov, 2022, 10:55 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" ?
>>>
>>>
>>>
>>>
>>>> On Thu, 17 Nov, 2022, 8:44 am Pavel Stehule, <pavel.stehule@gmail.com>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> 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
>>>>>
>>>>>
>>>>>>
>>>>>> regards, tom lane
>>>>>>
>>>>>
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-17 12:32 shashidhar Reddy <shashidharreddy001@gmail.com>
parent: shashidhar Reddy <shashidharreddy001@gmail.com>
0 siblings, 1 reply; 25+ messages in thread
From: shashidhar Reddy @ 2022-11-17 12:32 UTC (permalink / raw)
To: Pavel Stehule <pavel.stehule@gmail.com>; +Cc: Tom Lane <tgl@sss.pgh.pa.us>; pgsql-general
If I remove plpgsql_check getting below error
26: ERROR: 58P01: could not access file "$libdir/plpgsql_check": No such
file or directory
LOCATION: internal_load_library, dfmgr.c:211
If I drop only the extension (plpgsql_check) getting below error
psql:install.sql:122: ERROR: function plpgsql_check_function(oid) does not
exist
LINE 1: SELECT p.oid, n.nspname, p.proname, plpgsql_check_function(p...
^
On Thu, Nov 17, 2022 at 11:52 AM shashidhar Reddy <
shashidharreddy001@gmail.com> wrote:
> Ok, I will check.
>
> On Thu, 17 Nov, 2022, 11:35 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
>>
>>
>>>
>>> On Thu, 17 Nov, 2022, 10:55 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" ?
>>>>
>>>>
>>>>
>>>>
>>>>> On Thu, 17 Nov, 2022, 8:44 am Pavel Stehule, <pavel.stehule@gmail.com>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> 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
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> regards, tom lane
>>>>>>>
>>>>>>
--
Shashidhar
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-17 13:57 Pavel Stehule <pavel.stehule@gmail.com>
parent: shashidhar Reddy <shashidharreddy001@gmail.com>
0 siblings, 1 reply; 25+ messages in thread
From: Pavel Stehule @ 2022-11-17 13:57 UTC (permalink / raw)
To: shashidhar Reddy <shashidharreddy001@gmail.com>; +Cc: Tom Lane <tgl@sss.pgh.pa.us>; pgsql-general
čt 17. 11. 2022 v 13:32 odesílatel shashidhar Reddy <
shashidharreddy001@gmail.com> napsal:
> If I remove plpgsql_check getting below error
> 26: ERROR: 58P01: could not access file "$libdir/plpgsql_check": No such
> file or directory
> LOCATION: internal_load_library, dfmgr.c:211
>
> If I drop only the extension (plpgsql_check) getting below error
> psql:install.sql:122: ERROR: function plpgsql_check_function(oid) does
> not exist
> LINE 1: SELECT p.oid, n.nspname, p.proname, plpgsql_check_function(p...
>
you should to remove plpgsql_check by DROP EXTENSION plpgsql_check (only
this way). plpgsql_check is just language checker. Why it is called by your
application?
> ^
>
> On Thu, Nov 17, 2022 at 11:52 AM shashidhar Reddy <
> shashidharreddy001@gmail.com> wrote:
>
>> Ok, I will check.
>>
>> On Thu, 17 Nov, 2022, 11:35 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
>>>
>>>
>>>>
>>>> On Thu, 17 Nov, 2022, 10:55 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" ?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> On Thu, 17 Nov, 2022, 8:44 am Pavel Stehule, <pavel.stehule@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> regards, tom lane
>>>>>>>>
>>>>>>>
>
> --
> Shashidhar
>
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-17 14:02 shashidhar Reddy <shashidharreddy001@gmail.com>
parent: Pavel Stehule <pavel.stehule@gmail.com>
0 siblings, 1 reply; 25+ messages in thread
From: shashidhar Reddy @ 2022-11-17 14:02 UTC (permalink / raw)
To: Pavel Stehule <pavel.stehule@gmail.com>; +Cc: Tom Lane <tgl@sss.pgh.pa.us>; pgsql-general
Pavel,
I just dropped the extension, thats where I got the second error.
Looks like when any plpgsql functions runs it us looking for plpgsql_check.
On Thu, 17 Nov, 2022, 7:28 pm Pavel Stehule, <pavel.stehule@gmail.com>
wrote:
>
>
> čt 17. 11. 2022 v 13:32 odesílatel shashidhar Reddy <
> shashidharreddy001@gmail.com> napsal:
>
>> If I remove plpgsql_check getting below error
>> 26: ERROR: 58P01: could not access file "$libdir/plpgsql_check": No such
>> file or directory
>> LOCATION: internal_load_library, dfmgr.c:211
>>
>> If I drop only the extension (plpgsql_check) getting below error
>> psql:install.sql:122: ERROR: function plpgsql_check_function(oid) does
>> not exist
>> LINE 1: SELECT p.oid, n.nspname, p.proname, plpgsql_check_function(p...
>>
>
> you should to remove plpgsql_check by DROP EXTENSION plpgsql_check (only
> this way). plpgsql_check is just language checker. Why it is called by your
> application?
>
>
>
>> ^
>>
>> On Thu, Nov 17, 2022 at 11:52 AM shashidhar Reddy <
>> shashidharreddy001@gmail.com> wrote:
>>
>>> Ok, I will check.
>>>
>>> On Thu, 17 Nov, 2022, 11:35 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
>>>>
>>>>
>>>>>
>>>>> On Thu, 17 Nov, 2022, 10:55 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" ?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> On Thu, 17 Nov, 2022, 8:44 am Pavel Stehule, <
>>>>>>> pavel.stehule@gmail.com> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> 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
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> regards, tom lane
>>>>>>>>>
>>>>>>>>
>>
>> --
>> Shashidhar
>>
>
^ permalink raw reply [nested|flat] 25+ messages in thread
* Re: unrecognized node type: 350
@ 2022-11-17 14:52 Pavel Stehule <pavel.stehule@gmail.com>
parent: shashidhar Reddy <shashidharreddy001@gmail.com>
0 siblings, 0 replies; 25+ messages in thread
From: Pavel Stehule @ 2022-11-17 14:52 UTC (permalink / raw)
To: shashidhar Reddy <shashidharreddy001@gmail.com>; +Cc: Tom Lane <tgl@sss.pgh.pa.us>; pgsql-general
čt 17. 11. 2022 v 15:02 odesílatel shashidhar Reddy <
shashidharreddy001@gmail.com> napsal:
> Pavel,
>
> I just dropped the extension, thats where I got the second error.
> Looks like when any plpgsql functions runs it us looking for plpgsql_check.
>
Try to remove it - it does not sense on the production server.
> On Thu, 17 Nov, 2022, 7:28 pm Pavel Stehule, <pavel.stehule@gmail.com>
> wrote:
>
>>
>>
>> čt 17. 11. 2022 v 13:32 odesílatel shashidhar Reddy <
>> shashidharreddy001@gmail.com> napsal:
>>
>>> If I remove plpgsql_check getting below error
>>> 26: ERROR: 58P01: could not access file "$libdir/plpgsql_check": No
>>> such file or directory
>>> LOCATION: internal_load_library, dfmgr.c:211
>>>
>>> If I drop only the extension (plpgsql_check) getting below error
>>> psql:install.sql:122: ERROR: function plpgsql_check_function(oid) does
>>> not exist
>>> LINE 1: SELECT p.oid, n.nspname, p.proname, plpgsql_check_function(p...
>>>
>>
>> you should to remove plpgsql_check by DROP EXTENSION plpgsql_check (only
>> this way). plpgsql_check is just language checker. Why it is called by your
>> application?
>>
>>
>>
>>> ^
>>>
>>> On Thu, Nov 17, 2022 at 11:52 AM shashidhar Reddy <
>>> shashidharreddy001@gmail.com> wrote:
>>>
>>>> Ok, I will check.
>>>>
>>>> On Thu, 17 Nov, 2022, 11:35 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
>>>>>
>>>>>
>>>>>>
>>>>>> On Thu, 17 Nov, 2022, 10:55 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" ?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> On Thu, 17 Nov, 2022, 8:44 am Pavel Stehule, <
>>>>>>>> pavel.stehule@gmail.com> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> regards, tom lane
>>>>>>>>>>
>>>>>>>>>
>>>
>>> --
>>> Shashidhar
>>>
>>
^ permalink raw reply [nested|flat] 25+ messages in thread
end of thread, other threads:[~2022-11-17 14:52 UTC | newest]
Thread overview: 25+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-11-16 08:23 unrecognized node type: 350 shashidhar Reddy <shashidharreddy001@gmail.com>
2022-11-16 11:48 ` shashidhar Reddy <shashidharreddy001@gmail.com>
2022-11-16 12:56 ` Daniel Gustafsson <daniel@yesql.se>
2022-11-16 13:48 ` shashidhar Reddy <shashidharreddy001@gmail.com>
2022-11-16 14:27 ` Tom Lane <tgl@sss.pgh.pa.us>
2022-11-16 15:55 ` shashidhar Reddy <shashidharreddy001@gmail.com>
2022-11-16 16:02 ` Tom Lane <tgl@sss.pgh.pa.us>
2022-11-16 16:06 ` shashidhar Reddy <shashidharreddy001@gmail.com>
2022-11-16 16:18 ` Tom Lane <tgl@sss.pgh.pa.us>
2022-11-16 16:33 ` shashidhar Reddy <shashidharreddy001@gmail.com>
2022-11-16 16:36 ` Tom Lane <tgl@sss.pgh.pa.us>
2022-11-16 18:01 ` shashidhar Reddy <shashidharreddy001@gmail.com>
2022-11-16 18:21 ` Tom Lane <tgl@sss.pgh.pa.us>
2022-11-16 18:25 ` Pavel Stehule <pavel.stehule@gmail.com>
2022-11-16 18:52 ` Tom Lane <tgl@sss.pgh.pa.us>
2022-11-17 03:13 ` Pavel Stehule <pavel.stehule@gmail.com>
2022-11-17 05:18 ` shashidhar Reddy <shashidharreddy001@gmail.com>
2022-11-17 05:24 ` Pavel Stehule <pavel.stehule@gmail.com>
2022-11-17 05:55 ` shashidhar Reddy <shashidharreddy001@gmail.com>
2022-11-17 06:04 ` Pavel Stehule <pavel.stehule@gmail.com>
2022-11-17 06:22 ` shashidhar Reddy <shashidharreddy001@gmail.com>
2022-11-17 12:32 ` shashidhar Reddy <shashidharreddy001@gmail.com>
2022-11-17 13:57 ` Pavel Stehule <pavel.stehule@gmail.com>
2022-11-17 14:02 ` shashidhar Reddy <shashidharreddy001@gmail.com>
2022-11-17 14:52 ` Pavel Stehule <pavel.stehule@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox