Re: long lasting select, no io nor cpu usage ?

From: Franck Routier <franck(dot)routier(at)axege(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: long lasting select, no io nor cpu usage ?
Date: 2014-03-20 16:27:17
Message-ID: 532B16E5.9000403@axege.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Stefan Keller 2014-03-20 16:53:58 Getting query plan alternatives from query planner?
Previous Message Tom Lane 2014-03-20 14:15:03 Re: long lasting select, no io nor cpu usage ?