Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id D4B621337B83 for ; Wed, 11 May 2011 19:26:58 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 88862-09 for ; Wed, 11 May 2011 22:26:52 +0000 (UTC) X-Greylist: delayed 00:06:37.737928 by SQLgrey-1.7.6 Received: from na3sys009aog107.obsmtp.com (na3sys009aog107.obsmtp.com [74.125.149.197]) by mail.postgresql.org (Postfix) with ESMTP id 5E9701337B80 for ; Wed, 11 May 2011 19:26:51 -0300 (ADT) Received: from mail-qw0-f46.google.com ([209.85.216.46]) (using TLSv1) by na3sys009aob107.postini.com ([74.125.148.12]) with SMTP ID DSNKTcsNKpmMrYp66e24vYy9aIEEUvIHoJiJ@postini.com; Wed, 11 May 2011 15:26:52 PDT Received: by mail-qw0-f46.google.com with SMTP id 3so498608qwk.19 for ; Wed, 11 May 2011 15:26:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.183.78 with SMTP id cf14mr8353430qab.396.1305152411810; Wed, 11 May 2011 15:20:11 -0700 (PDT) Received: by 10.224.47.70 with HTTP; Wed, 11 May 2011 15:20:11 -0700 (PDT) Date: Wed, 11 May 2011 15:20:11 -0700 Message-ID: Subject: When does postgres set the connection state back to idle? From: Stephen Sugden To: pgsql-admin@postgresql.org Content-Type: multipart/alternative; boundary=20cf303b39ade23a5104a307799e X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.899 tagged_above=-10 required=5 tests=BAYES_00=-1.9, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 201105/85 X-Sequence-Number: 37522 --20cf303b39ade23a5104a307799e Content-Type: text/plain; charset=ISO-8859-1 I've been having a difficult time finding an answer for this via google, so please excuse me if this is the wrong list, or a stupid question... We're trying to diagnose a system issue where we ended up with 100's of non-idle queries in pg_stat_activity, but the actual system load didn't correspond to what we should have seen with that query load. Is it possible that a client could cause this by not acknowledging that it has received results, so that postgres will think the query is active even when it's done the hard work of getting the queried data off disk? These were all SELECT queries if that makes any difference. -Stephen --20cf303b39ade23a5104a307799e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I've been having a difficult time finding an answer for this via google= , so please excuse me if this is the wrong list, or a stupid question...
We're trying to diagnose a system issue where we ended up with 100= 's of non-idle queries in pg_stat_activity, but the actual system load = didn't correspond to what we should have seen with that query load. Is = it possible that a client could cause this by not acknowledging that it has= received results, so that postgres will think the query is active even whe= n it's done the hard work of getting the queried data off disk? These w= ere all SELECT queries if that makes any difference.

-Stephen
--20cf303b39ade23a5104a307799e--