Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id EC1FB9FAE4E for ; Thu, 28 Sep 2006 12:28:56 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 12081-02 for ; Thu, 28 Sep 2006 12:28:51 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by postgresql.org (Postfix) with ESMTP id 2C3F69FB319 for ; Thu, 28 Sep 2006 12:28:46 -0300 (ADT) Received: from collaborativefusion.com (mx01.pub.collaborativefusion.com [206.210.89.201]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Thu, 28 Sep 2006 11:28:45 -0400 id 0005643B.451BEA2D.00004B35 Received: from Internal Mail-Server (206.210.89.202) by mx01 (envelope-from wmoran@collaborativefusion.com) with AES256-SHA encrypted SMTP; 28 Sep 2006 11:26:35 -0400 Date: Thu, 28 Sep 2006 11:28:43 -0400 From: Bill Moran To: Matthew Schumacher Cc: pgsql-performance@postgresql.org Subject: Re: Problems with inconsistant query performance. Message-Id: <20060928112843.0b6e3715.wmoran@collaborativefusion.com> In-Reply-To: <451BE7CD.3060807@aptalaska.net> References: <451AC4E2.90106@aptalaska.net> <1c9501c6e2fb$91e30200$0c67a8c0@maniek> <451BE7CD.3060807@aptalaska.net> Organization: Collaborative Fusion X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.20; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.072 tagged_above=0 required=5 tests=AWL, UNPARSEABLE_RELAY X-Spam-Level: X-Archive-Number: 200609/384 X-Sequence-Number: 21070 In response to Matthew Schumacher : > > What I really need is a way to profile my proc when it runs slow so that > I can resolve which of the queries is really slow. Anyone with an idea > on how to do this? You could turn on statement logging and duration logging. This would give you a record of when things run and how long they take. A little work analyzing should show you which queries are running when your favorite query slows down. -- Bill Moran Collaborative Fusion Inc.