Re: unrecognized node type: 350

2022-11-16 Thread shashidhar Reddy
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

Re: unrecognized node type: 350

2022-11-16 Thread Pavel Stehule
č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

Re: unrecognized node type: 350

2022-11-16 Thread shashidhar Reddy
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

Re: unrecognized node type: 350

2022-11-16 Thread Pavel Stehule
č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

Re: unrecognized node type: 350

2022-11-16 Thread shashidhar Reddy
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

Re: unrecognized node type: 350

2022-11-16 Thread Pavel Stehule
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]:

Re: unrecognized node type: 350

2022-11-16 Thread Tom Lane
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

Re: unrecognized node type: 350

2022-11-16 Thread Pavel Stehule
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

Re: unrecognized node type: 350

2022-11-16 Thread Tom Lane
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

Re: unrecognized node type: 350

2022-11-16 Thread shashidhar Reddy
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 >

Re: PostgreSQL server "idle in transaction"

2022-11-16 Thread Adrian Klaver
On 11/16/22 12:51 AM, Matthias Apitz wrote: El día Dienstag, November 15, 2022 a las 10:28:11 -0500, Tom Lane escribió: Adrian Klaver writes: On 11/15/22 04:28, Matthias Apitz wrote: I have below the full ESQL/C log and do not understand, why the PostgreSQL server is thinking "idle in

Re: PANIC: could not flush dirty data: Cannot allocate memory

2022-11-16 Thread Andres Freund
Hi, On 2022-11-16 09:16:56 -0800, Andres Freund wrote: > On 2022-11-15 13:23:56 +0100, klaus.mailingli...@pernau.at wrote: > > Filesystem is ext4. VM technology is mixed: VMware, KVM and XEN PV. Kernel > > is 5.15.0-52-generic. > > > > We have not seen this with Ubutnu 18.04 and 20.04 (although

Re: PANIC: could not flush dirty data: Cannot allocate memory

2022-11-16 Thread Andres Freund
Hi, On 2022-11-15 13:23:56 +0100, klaus.mailingli...@pernau.at wrote: > Filesystem is ext4. VM technology is mixed: VMware, KVM and XEN PV. Kernel > is 5.15.0-52-generic. > > We have not seen this with Ubutnu 18.04 and 20.04 (although we might not > have noticed it). Did this start after

Re: unrecognized node type: 350

2022-11-16 Thread Tom Lane
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

Re: unrecognized node type: 350

2022-11-16 Thread shashidhar Reddy
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: >

Re: unrecognized node type: 350

2022-11-16 Thread Tom Lane
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

Re: unrecognized node type: 350

2022-11-16 Thread shashidhar Reddy
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

Re: unrecognized node type: 350

2022-11-16 Thread Tom Lane
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.

Re: unrecognized node type: 350

2022-11-16 Thread shashidhar Reddy
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

Re: pg_restore remap schema

2022-11-16 Thread Thomas Kellerer
Tom Lane schrieb am 08.08.2022 um 20:22: > Guillaume Lelarge writes: >> Le lun. 8 août 2022 à 18:28, Fabrice Chapuis a >>> Is a development in progress to add this option > >> Nope, never heard of someone working on this. > > People have asked for such a thing before, but it'd be quite difficult

Re: pg_restore remap schema

2022-11-16 Thread Tom Lane
=?UTF-8?Q?St=C3=A9phane_Tachoires?= writes: > And could it be at pg_dump level ? > It seems more aware of what is doing... pg_dump would be in a slightly better position, but only slightly. It still has no idea about the contents of function bodies. Also, if it's acceptable to do this at dump

Re: pg_restore remap schema

2022-11-16 Thread Stéphane Tachoires
Hi And could it be at pg_dump level ? It seems more aware of what is doing... Stephane Le mer. 16 nov. 2022 à 15:42, Tom Lane a écrit : > Guillaume Lelarge writes: > > Le mer. 16 nov. 2022 à 13:08, Fabrice Chapuis > a > > écrit : > >> I worked on the pg_dump source code to add remap schema

Re: pg_restore remap schema

2022-11-16 Thread Tom Lane
Guillaume Lelarge writes: > Le mer. 16 nov. 2022 à 13:08, Fabrice Chapuis a > écrit : >> I worked on the pg_dump source code to add remap schema functionality to >> use it internally where I work. This is a first version that allows to >> remap tables, views and sequences (only to export

Re: unrecognized node type: 350

2022-11-16 Thread Tom Lane
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 the like)?

Re: An I/O error occured while sending to the backend

2022-11-16 Thread Rob Sargent
On 11/16/22 00:37, gzh wrote: Thank you very much for your advice. What I don't understand is that there is no problem when executing ① alone or ② alone, the error occurs when ① and ② are executed together . It works well when i let the application sleep after ① for 10 seconds before

Re: unrecognized node type: 350

2022-11-16 Thread shashidhar Reddy
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 the issue? > >

Re: pg_restore remap schema

2022-11-16 Thread Guillaume Lelarge
Hi, Le mer. 16 nov. 2022 à 13:08, Fabrice Chapuis a écrit : > Hi, > I worked on the pg_dump source code to add remap schema functionality to > use it internally where I work. This is a first version that allows to > remap tables, views and sequences (only to export schema). Is this >

Re: unrecognized node type: 350

2022-11-16 Thread Daniel Gustafsson
> 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 - > 2022-11-16-02:28:08 -

Re: PostgreSQL server "idle in transaction"

2022-11-16 Thread Matthias Apitz
El día Dienstag, November 15, 2022 a las 10:28:11 -0500, Tom Lane escribió: > Adrian Klaver writes: > > On 11/15/22 04:28, Matthias Apitz wrote: > >> I have below the full ESQL/C log and do not understand, why the > >> PostgreSQL server is thinking "idle in transaction". For me with the > >>

Re: pg_restore remap schema

2022-11-16 Thread Fabrice Chapuis
Hi, I worked on the pg_dump source code to add remap schema functionality to use it internally where I work. This is a first version that allows to remap tables, views and sequences (only to export schema). Is this development likely to interest the PG community and to continue this development

Re: unrecognized node type: 350

2022-11-16 Thread shashidhar Reddy
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-16 02:28:08,957 DEBUG

Re: PostgreSQL server "idle in transaction"

2022-11-16 Thread Matthias Apitz
El día Dienstag, November 15, 2022 a las 10:28:11 -0500, Tom Lane escribió: > Adrian Klaver writes: > > On 11/15/22 04:28, Matthias Apitz wrote: > >> I have below the full ESQL/C log and do not understand, why the > >> PostgreSQL server is thinking "idle in transaction". For me with the > >>

unrecognized node type: 350

2022-11-16 Thread shashidhar Reddy
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