Re: bug report: All queries incorrectly shown as blocking in server status

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Chris St Denis <chris(at)ctgameinfo(dot)com>
Cc: pgadmin-support(at)postgresql(dot)org, Sachin Srivastava <sachin(dot)srivastava(at)enterprisedb(dot)com>
Subject: Re: bug report: All queries incorrectly shown as blocking in server status
Date: 2012-10-29 13:21:45
Message-ID: CA+OCxoyO9DsyJPsAQp26+g2UsM4edZNW05woQ-bmEs9hKToVPw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Sachin, can you look into this please? Thanks.

On Thu, Oct 25, 2012 at 11:08 PM, Chris St Denis <chris(at)ctgameinfo(dot)com> wrote:
> Platform: Windows 7
> Language: English
> Dist: Binary Windows download from official site
> Version: 1.16.0
>
>
> As shown in attached screenshot.png all queries are shown as blocked by one
> of my queries. This is obviously incorrect since idle queries and queries
> from different databases are shown as blocked.
>
> A select from pg_stat_activity confirms that only 1 query (49244) is
> actually waiting (it is likely it is waiting on the 47825 that they are all
> reported as waiting on)
>
> select pid, waiting, state from pg_stat_activity;
> pid | waiting | state
> -------+---------+--------
> 58614 | f | idle
> 47225 | f | idle
> 48655 | f | idle
> 33051 | f | idle
> 58615 | f | idle
> 58726 | f | idle
> 48306 | f | idle
> 33054 | f | idle
> 48865 | f | idle
> 47819 | f | active
> 53037 | f | idle
> 47820 | f | active
> 49244 | t | active
> 45059 | f | active
> 44561 | f | idle
> 55098 | f | idle
> 47822 | f | active
> 52394 | f | idle
> 55058 | f | idle
> 34636 | f | idle
> 34642 | f | idle
> 45180 | f | idle
> 34718 | f | idle
> 45201 | f | idle
> 45585 | f | idle
> 44131 | f | idle
> 52395 | f | idle
> 50221 | f | idle
> 45397 | f | idle
> 47824 | f | active
> 49978 | f | idle
> 47825 | f | active
> 45414 | f | active
> 50520 | f | idle
> 54395 | f | idle
> 52825 | f | idle
> 11791 | f | active
> 53040 | f | idle
> 53043 | f | idle
> 53057 | f | idle
> 47823 | f | active
> 48659 | f | idle
> 53892 | f | idle
> 53056 | f | idle
> 53058 | f | idle
> 53893 | f | idle
> 53894 | f | idle
> 47835 | f | idle
> 46732 | f | idle
> 55059 | f | idle
> 53895 | f | idle
> 53896 | f | idle
> 47837 | f | idle
> 53897 | f | idle
> 47843 | f | idle
> 47845 | f | active
> 48658 | f | idle
> 48694 | f | idle
> 48868 | f | idle
> 48870 | f | idle
> 48893 | f | idle
> 48972 | f | idle
> 50526 | f | idle
> (63 rows)
>
>
>
> --
> Sent via pgadmin-support mailing list (pgadmin-support(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgadmin-support
>

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Michael Pfütz 2012-10-31 08:18:41 wish: Data Collapse / Expand Mode looks like phpPgAdmin
Previous Message Dave Page 2012-10-29 11:33:32 Re: No more Delete/Drop constraints in 1.16