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 2BC2AD76E3; Thu, 25 Aug 2005 16:55:19 -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 77560-05; Thu, 25 Aug 2005 19:55:17 +0000 (GMT) Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by svr1.postgresql.org (Postfix) with ESMTP id 31554D76AE; Thu, 25 Aug 2005 16:55:14 -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 j7PJt9I9017989 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 25 Aug 2005 13:55:12 -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 j7PJt9c8054127; Thu, 25 Aug 2005 13:55:09 -0600 (MDT) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.3/8.13.3/Submit) id j7PJt9Uf054126; Thu, 25 Aug 2005 13:55:09 -0600 (MDT) (envelope-from mfuhr) Date: Thu, 25 Aug 2005 13:55:09 -0600 From: Michael Fuhr To: "Marc G. Fournier" Cc: Aldor , pgsql-admin@postgresql.org Subject: Re: What is syslog:duration reporting ... ? Message-ID: <20050825195508.GA54074@winnie.fuhr.org> References: <20050825152428.T1044@ganymede.hub.org> <430E12F1.1080206@mediaroot.de> <20050825155331.V1044@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050825155331.V1044@ganymede.hub.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/323 X-Sequence-Number: 18642 On Thu, Aug 25, 2005 at 03:56:36PM -0300, Marc G. Fournier wrote: > On Thu, 25 Aug 2005, Aldor wrote: > >I'm still wondering why you first query takes about 4107.987 ms - this > >kind of query has usually have to run much much faster. > > That would work if I were to get really occasional high values in syslog, > but this is almost a consist thing over a very short period of time: 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. -- Michael Fuhr