From: Franck Routier <franck.routier@axege.com>
To: pgsql-performance@postgresql.org
Subject: Re: long lasting select, no io nor cpu usage ?
Date: Thu, 20 Mar 2014 17:27:17 +0100
Message-ID: <532B16E5.9000403@axege.com> (raw)
In-Reply-To: <2749.1395324903@sss.pgh.pa.us>
References: <532AF271.4040903@axege.com>
<2042.1395323785@sss.pgh.pa.us>
<532AF623.2040502@axege.com>
<2749.1395324903@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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
Attachments:
smime.p7s (application/pkcs7-signature, 4.2K) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: franck.routier@axege.com
Subject: Re: long lasting select, no io nor cpu usage ?
In-Reply-To: <532B16E5.9000403@axege.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox