From: Tom Lane <tgl@sss.pgh.pa.us>
To: Franck Routier <franck.routier@axege.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: long lasting select, no io nor cpu usage ?
Date: Thu, 20 Mar 2014 10:15:03 -0400
Message-ID: <2749.1395324903@sss.pgh.pa.us> (raw)
In-Reply-To: <532AF623.2040502@axege.com>
References: <532AF271.4040903@axege.com>
<2042.1395323785@sss.pgh.pa.us>
<532AF623.2040502@axege.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
Franck Routier <franck.routier@axege.com> writes:
> Le 20/03/2014 14:56, Tom Lane a écrit :
>> pg_locks, probably. regards, tom lane
> select * from pg_stat_activity shows 'F'alse in the waiting column for
> the query.
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
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
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: tgl@sss.pgh.pa.us, franck.routier@axege.com
Subject: Re: long lasting select, no io nor cpu usage ?
In-Reply-To: <2749.1395324903@sss.pgh.pa.us>
* 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