X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 5FF35D71F0; Thu, 25 Aug 2005 16:59:49 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 80440-03; Thu, 25 Aug 2005 19:59:45 +0000 (GMT) Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by svr1.postgresql.org (Postfix) with ESMTP id 75ABAD6FEC; Thu, 25 Aug 2005 16:59:44 -0300 (ADT) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.3/8.13.3) with ESMTP id j7PJxfgB017992 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 25 Aug 2005 13:59:44 -0600 (MDT) (envelope-from mfuhr@winnie.fuhr.org) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.3/8.13.3) with ESMTP id j7PJxfZd054182; Thu, 25 Aug 2005 13:59:41 -0600 (MDT) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.3/8.13.3/Submit) id j7PJxeH8054181; Thu, 25 Aug 2005 13:59:40 -0600 (MDT) (envelope-from mfuhr) Date: Thu, 25 Aug 2005 13:59:40 -0600 From: Michael Fuhr To: "Marc G. Fournier" Cc: Aldor , pgsql-admin@postgresql.org Subject: Re: What is syslog:duration reporting ... ? Message-ID: <20050825195940.GA54140@winnie.fuhr.org> References: <20050825152428.T1044@ganymede.hub.org> <430E12F1.1080206@mediaroot.de> <20050825155331.V1044@ganymede.hub.org> <20050825195508.GA54074@winnie.fuhr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050825195508.GA54074@winnie.fuhr.org> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.005 required=5 tests=[AWL=0.005] X-Spam-Level: X-Archive-Number: 200508/324 X-Sequence-Number: 18643 On Thu, Aug 25, 2005 at 01:55:08PM -0600, Michael Fuhr wrote: > Are the updates happening inside a transaction? Is it possible > that they're being blocked by other transactions that update the > same record around the same time and don't commit immediately? > I can duplicate the results you're seeing by doing that. As for why you don't see long durations with EXPLAIN ANALYZE, here's a possible explanation: "ordinary" updates of the same record might happen close together because that's how the application works, but by the time you run EXPLAIN ANALYZE no other transactions are updating that record so the update executes immediately. -- Michael Fuhr