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 25B82D7793; Fri, 26 Aug 2005 10:27:18 -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 84291-02; Fri, 26 Aug 2005 13:27:16 +0000 (GMT) Received: from 217-20-115-93.internetserviceteam.com (217-20-115-93.internetserviceteam.com [217.20.115.93]) by svr1.postgresql.org (Postfix) with ESMTP id F1931D7017; Fri, 26 Aug 2005 10:27:14 -0300 (ADT) Received: from [192.168.1.123] (91.Red-83-33-222.pooles.rima-tde.net [83.33.222.91]) by 217-20-115-93.internetserviceteam.com (Postfix) with ESMTP id 3586B395ED; Fri, 26 Aug 2005 14:38:09 +0200 (CEST) Message-ID: <430F18A8.8030401@mediaroot.de> Date: Fri, 26 Aug 2005 14:27:04 +0100 From: Aldor User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Fuhr Cc: "Marc G. Fournier" , pgsql-admin@postgresql.org Subject: Re: What is syslog:duration reporting ... ? References: <20050825152428.T1044@ganymede.hub.org> <430E12F1.1080206@mediaroot.de> <20050825155331.V1044@ganymede.hub.org> <20050825195508.GA54074@winnie.fuhr.org> <20050825195940.GA54140@winnie.fuhr.org> <430E5945.4000408@mediaroot.de> <20050826013121.GA89046@winnie.fuhr.org> In-Reply-To: <20050826013121.GA89046@winnie.fuhr.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 required=5 tests=[none] X-Spam-Level: X-Archive-Number: 200508/351 X-Sequence-Number: 18670 Aug 25 14:53:33 forgehouse-s1 postgres[23723]: [2-1] LOG: duration: > 1192.789 ms statement: UPDATE session SET hit_time=now() WHERE > md5='d84613009a95296fb511c2cb051ad618'; > Aug 25 14:53:53 forgehouse-s1 postgres[23727]: [2-1] LOG: duration: > 12159.162 ms statement: UPDATE session SET hit_time=now() WHERE > md5='d84613009a95296fb511c2cb051ad618'; 20 seconds - 13 seconds (execution time) = 7 seconds So it also happens when they are not close to each other. The hint with the log_min_duration is a good idea. Michael Fuhr wrote: > On Fri, Aug 26, 2005 at 12:50:29AM +0100, Aldor wrote: > >>Aug 25 14:53:32 forgehouse-s1 postgres[23721]: [2-1] LOG: duration: >>567.559 ms statement: UPDATE session SET hit_time=now() WHERE >>md5='7537b74eab488de54d6e0167d1919207'; >>Aug 25 14:53:32 forgehouse-s1 postgres[23722]: [2-1] LOG: duration: >>565.966 ms statement: UPDATE session SET hit_time=now() WHERE >>md5='d84613009a95296fb511c2cb051ad618'; >>Aug 25 14:53:33 forgehouse-s1 postgres[23723]: [2-1] LOG: duration: >>1192.789 ms statement: UPDATE session SET hit_time=now() WHERE >>md5='d84613009a95296fb511c2cb051ad618'; >>Aug 25 14:53:53 forgehouse-s1 postgres[23727]: [2-1] LOG: duration: >>12159.162 ms statement: UPDATE session SET hit_time=now() WHERE >>md5='d84613009a95296fb511c2cb051ad618'; >>Aug 25 14:53:54 forgehouse-s1 postgres[23728]: [2-1] LOG: duration: >>3283.185 ms statement: UPDATE session SET hit_time=now() WHERE >>md5='7537b74eab488de54d6e0167d1919207'; >>Aug 25 14:53:57 forgehouse-s1 postgres[23729]: [2-1] LOG: duration: >>2116.516 ms statement: UPDATE session SET hit_time=now() WHERE >>md5='7537b74eab488de54d6e0167d1919207'; >> >>Take a look to the timestamps... they are not really close to each other... > > > Eh? The timestamps show that the updates *are* close to each other. > What we don't know is whether this log excerpt shows all statements > that were executed during its time frame. It might have been grep'ed > from the full log file, or the log_min_duration_statement setting > might be such that only statements lasting more than a certain > amount of time are logged and we're not seeing similar updates that > happened quickly, nor when any of the updates were committed. > > Marc, does my hypothesis of updates being blocked by other transactions > sound plausible in your environment? How complete a log did you > post -- is it everything, or are there other statements that you > omitted or that weren't logged because of the log_min_duration_statement > setting? >