Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 665949FB306; Fri, 29 Sep 2006 22:24:04 -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 52745-05; Fri, 29 Sep 2006 22:24:01 -0300 (ADT) X-Greylist: delayed 00:30:07.869483 by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 0EF829FB224; Fri, 29 Sep 2006 22:24:00 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from dantes.bytestacker.com (dantes.bytestacker.com [209.40.97.141]) by svr4.postgresql.org (Postfix) with ESMTP id AEE7D5AF8B5; Sat, 30 Sep 2006 00:53:51 +0000 (GMT) Received: from domino1.bytestacker.com (dantes.bytestacker.com [172.16.16.11]) by dantes.bytestacker.com (Postfix) with ESMTP id 3F6DE3BBFB; Fri, 29 Sep 2006 19:54:33 -0500 (CDT) Importance: Normal X-Priority: 3 (Normal) Subject: Re: Postgres locking up? Date: Fri, 29 Sep 2006 19:53:46 -0500 From: Robert Becker Cope To: bhurt@janestcapital.com, pgsql-performance@postgresql.org, pgsql-novice@postgresql.org X-Mailer: IBM Lotus Domino Access for MS Outlook (2003) Build V702_07192006 July 19, 2006 Message-ID: X-MIMETrack: Serialize by Router on domino1/ByteStacker(Release 7.0.1|January 17, 2006) at 09/29/2006 07:54:32 PM MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.384 tagged_above=0 required=5 tests=SPF_SOFTFAIL X-Spam-Level: * X-Archive-Number: 200609/440 X-Sequence-Number: 21126 Brian Hurt wrote: > I'm experiencing a problem with our postgres database. Queries that > normally take seconds suddenly start taking hours, if they complete at > all. Do you have any long running transactions? I have noticed that with Postgres 8.1.x, a long running transaction combined with other transactions over a long enough time period can very predictably lead to this type of behavior One simple way to see if you have any long running transactions is to look for PIDs that are "idle in transaction" for long periods of time. robert