[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pgsql-performance
Subject:    Re: [PERFORM] long lasting select, no io nor cpu usage ?
From:       Franck Routier <franck.routier () axege ! com>
Date:       2014-03-20 16:27:17
Message-ID: 532B16E5.9000403 () axege ! com
[Download RAW message or body]


Le 20/03/2014 15:15, Tom Lane a =E9crit :
> Hm.  The next most likely theory is that it's waiting on network I/O,
> but it's hard to tell that from the outside.  Can you attach to the
> stuck backend with gdb and get a stack trace?
> http://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQ=
L_backend
>
> 			regards, tom lane
>
I found the problem, not related to postgresql after all.
The client (CloverETL, using jdbc) was stuck and not "consuming" the
records. I killed and restarted the ETL and all is fine now.

Thanks a lot for your time and help,

Franck


["smime.p7s" (application/pkcs7-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]