Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 70C289FA0B0 for ; Thu, 13 Sep 2007 12:10:17 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 28789-05 for ; Thu, 13 Sep 2007 12:10:12 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id D74939F9D97 for ; Thu, 13 Sep 2007 12:10:11 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l8DFA9mJ015181; Thu, 13 Sep 2007 11:10:09 -0400 (EDT) To: Brad Nicholson cc: pgsql-performance@postgresql.org Subject: Re: Long Running Commits - Not Checkpoints In-reply-to: <1189695802.8624.25.camel@bnicholson-desktop> References: <1189692915.8624.22.camel@bnicholson-desktop> <1189695802.8624.25.camel@bnicholson-desktop> Comments: In-reply-to Brad Nicholson message dated "Thu, 13 Sep 2007 11:03:22 -0400" Date: Thu, 13 Sep 2007 11:10:09 -0400 Message-ID: <15180.1189696209@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200709/247 X-Sequence-Number: 26792 Brad Nicholson writes: > On Thu, 2007-09-13 at 10:15 -0400, Brad Nicholson wrote: >> I'm having a problem with long running commits appearing in my database >> logs. It may be hardware related, as the problem appeared when we moved >> the database to a new server connected to a different disk array. > More on this - we also have long running commits on installations that > do have the wal files on a separate partition. What's your definition of "long running commit" --- seconds? milliseconds? Exactly what are you measuring? Can you correlate the problem with what the transaction was doing? regards, tom lane