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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Franck Routier <franck(dot)routier(at)axege(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: long lasting select, no io nor cpu usage ?
Date: 2014-03-20 14:15:03
Message-ID: 2749.1395324903@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Franck Routier <franck(dot)routier(at)axege(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Franck Routier 2014-03-20 16:27:17 Re: long lasting select, no io nor cpu usage ?
Previous Message Franck Routier 2014-03-20 14:07:31 Re: long lasting select, no io nor cpu usage ?