Re: long lasting select, no io nor cpu usage ? - Mailing list pgsql-performance

From Franck Routier
Subject Re: long lasting select, no io nor cpu usage ?
Date
Msg-id 532B16E5.9000403@axege.com
Whole thread Raw
In response to Re: long lasting select, no io nor cpu usage ?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
Le 20/03/2014 15:15, Tom Lane a écrit :
> 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_PostgreSQL_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


Attachment

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: long lasting select, no io nor cpu usage ?
Next
From: Stefan Keller
Date:
Subject: Getting query plan alternatives from query planner?