čt 17. 11. 2022 v 15:02 odesílatel shashidhar Reddy <
shashidharreddy...@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
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,
wrote:
>
>
> čt 17. 11. 2022 v 13:32 odesílatel shashidhar Reddy <
> shashidharreddy...@gmail.com>
čt 17. 11. 2022 v 13:32 odesílatel shashidhar Reddy <
shashidharreddy...@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
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
Ok, I will check.
On Thu, 17 Nov, 2022, 11:35 am Pavel Stehule,
wrote:
>
>
> čt 17. 11. 2022 v 6:55 odesílatel shashidhar Reddy <
> shashidharreddy...@gmail.com> napsal:
>
>> Show plpgsql_check.mode gives an error as unrecognized configuration
>> parameter.
>>
>> We use plprofiler
>>
>
> it
čt 17. 11. 2022 v 6:55 odesílatel shashidhar Reddy <
shashidharreddy...@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
Show plpgsql_check.mode gives an error as unrecognized configuration
parameter.
We use plprofiler
On Thu, 17 Nov, 2022, 10:55 am Pavel Stehule,
wrote:
>
>
> čt 17. 11. 2022 v 6:18 odesílatel shashidhar Reddy <
> shashidharreddy...@gmail.com> napsal:
>
>> Pavel,
>>
>> Plpgsql_check configured
čt 17. 11. 2022 v 6:18 odesílatel shashidhar Reddy <
shashidharreddy...@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
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,
wrote:
>
>
> st 16. 11. 2022 v 19:52 odesílatel Tom Lane napsal:
>
>> Pavel Stehule writes:
>> > st 16. 11. 2022 v 19:01 odesílatel shashidhar
st 16. 11. 2022 v 19:52 odesílatel Tom Lane napsal:
> Pavel Stehule writes:
> > st 16. 11. 2022 v 19:01 odesílatel shashidhar Reddy <
> > shashidharreddy...@gmail.com> napsal:
> >>> I could see an error in syslogs, I am not sure what it means.
> >>> kernel: [93631.415790] postgres[86383]:
Pavel Stehule writes:
> st 16. 11. 2022 v 19:01 odesílatel shashidhar Reddy <
> shashidharreddy...@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
>>> 7f07f3e3eefd
>>> sp 7fffcf1db500 error
Hi
st 16. 11. 2022 v 19:01 odesílatel shashidhar Reddy <
shashidharreddy...@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, wrote:
>
>> shashidhar Reddy writes:
>> > I could see an error in syslogs, I
shashidhar Reddy 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
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, wrote:
> shashidhar Reddy writes:
> > I could see an error in syslogs, I am not sure what it means.
> > kernel: [93631.415790] postgres[86383]: segfault at 80 ip
>
shashidhar Reddy writes:
> I could see an error in syslogs, I am not sure what it means.
> kernel: [93631.415790] postgres[86383]: segfault at 80 ip 7f07f3e3eefd
> sp 7fffcf1db500 error 4 in plpgsql_check.so[7f07f3e2e000+34000]
That would certainly suggest a problem in plpgsql_check.
It
I could see an error in syslogs, I am not sure what it means.
kernel: [93631.415790] postgres[86383]: segfault at 80 ip 7f07f3e3eefd
sp 7fffcf1db500 error 4 in plpgsql_check.so[7f07f3e2e000+34000]
On Wed, Nov 16, 2022 at 9:36 PM shashidhar Reddy <
shashidharreddy...@gmail.com> wrote:
>
shashidhar Reddy 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
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, wrote:
> shashidhar Reddy writes:
> > We have extensions like plpgsql_check and plprofiler.
>
> Hmm. My bet is that one of those
shashidhar Reddy 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.
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
shashidhar Reddy 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
We are using 42.2.21 jdbc version
On Wed, 16 Nov, 2022, 6:26 pm Daniel Gustafsson, wrote:
> > On 16 Nov 2022, at 09:23, shashidhar Reddy
> wrote:
>
> > We have upgraded postgresql from version 12 to 13.8 and after that
> facing unrecognized node type: 350, what could be t
> On 16 Nov 2022, at 09:23, shashidhar Reddy
> 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 -
> 2
Any help on this?
On Wed, 16 Nov, 2022, 1:53 pm shashidhar Reddy, <
shashidharreddy...@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-1
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
25 matches
Mail list logo
