X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id DED26D1E96F for ; Fri, 16 Apr 2004 12:46:09 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 70059-08 for ; Fri, 16 Apr 2004 12:46:03 -0300 (ADT) Received: from gw.tssi.com (gw.tssi.com [198.147.197.1]) by svr1.postgresql.org (Postfix) with ESMTP id 4A4C1D1E96C for ; Fri, 16 Apr 2004 12:46:07 -0300 (ADT) Received: from gw.tssi.com (nolan@gw.tssi.com [127.0.0.1] (may be forged)) by gw.tssi.com (8.12.6/8.12.6) with ESMTP id i3GFk48S010495; Fri, 16 Apr 2004 10:46:05 -0500 Received: (from nolan@localhost) by gw.tssi.com (8.12.6/8.12.6/Submit) id i3GFk3p3010490; Fri, 16 Apr 2004 10:46:03 -0500 From: Mike Nolan Message-Id: <200404161546.i3GFk3p3010490@gw.tssi.com> Subject: Re: Long running queries degrade performance To: chris.kratz@vistashare.com (Chris Kratz) Date: Fri, 16 Apr 2004 10:46:02 -0500 (CDT) Cc: pgsql-performance@postgresql.org In-Reply-To: <200404161128.00851.chris.kratz@vistashare.com> from "Chris Kratz" at Apr 16, 2004 11:28:00 AM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/212 X-Sequence-Number: 6512 > We have a web app with a postgres backend. Most queries have subsecond > response times through the web even with high usage. Every once in awhile > someone will run either an ad-hoc query or some other long running db > process. Are you sure it is postgres where the delay is occurring? I ask this because I also have a web-based front end to postgres, and while most of the time the queries respond in about a second every now and then I see one that takes much longer, sometimes 10-15 seconds. I've seen this behavior on both my development system and on the production server. The same query a while later might respond quickly again. I'm not sure where to look for the delay, either, and it is intermittent enough that I'm not even sure what monitoring techniques to use. -- Mike Nolan