Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 4A1969F981F for ; Fri, 14 Sep 2007 08:31:57 -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 42815-02 for ; Fri, 14 Sep 2007 08:31:49 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from proxy1.bredband.net (proxy1.bredband.net [195.54.101.71]) by postgresql.org (Postfix) with ESMTP id C863F9F980F for ; Fri, 14 Sep 2007 08:31:53 -0300 (ADT) Received: from zigo.dhs.org (83.227.204.174) by proxy1.bredband.net (7.3.127) id 46E9326100058BEC; Fri, 14 Sep 2007 13:31:46 +0200 Received: from zigo.dhs.org (zigo [127.0.0.1]) by zigo.dhs.org (Postfix) with ESMTP id C3B468640; Fri, 14 Sep 2007 13:31:45 +0200 (CEST) Received: from 192.121.104.48 (SquirrelMail authenticated user db) by zigo.dhs.org with HTTP; Fri, 14 Sep 2007 13:31:45 +0200 (CEST) Message-ID: <43618.192.121.104.48.1189769505.squirrel@zigo.dhs.org> In-Reply-To: <1189692915.8624.22.camel@bnicholson-desktop> References: <1189692915.8624.22.camel@bnicholson-desktop> Date: Fri, 14 Sep 2007 13:31:45 +0200 (CEST) Subject: Re: Long Running Commits - Not Checkpoints From: db@zigo.dhs.org To: "Brad Nicholson" Cc: pgsql-performance@postgresql.org User-Agent: SquirrelMail/1.4.8 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200709/273 X-Sequence-Number: 26818 > 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. The > disk array is a lower class array, but still more than powerful enough > to handle the IO requirements. One big difference though is that the > old array had 16 GB of cache, the new one has 4 GB. Maybe the old disk array had battery backed up ram that was used as a write cache and the new only has read cache? Without battery backed up ram (or flash or whatever) then a commit need to flush data down onto the pysical disk. /Dennis