pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Fuhr <mike@fuhr.org>
To: Aldor <an@mediaroot.de>
Cc: Marc G. Fournier <scrappy@postgresql.org>
Cc: pgsql-admin@postgresql.org
Subject: Re: What is syslog:duration reporting ... ?
Date: Thu, 25 Aug 2005 19:31:21 -0600
Message-ID: <20050826013121.GA89046@winnie.fuhr.org> (raw)
In-Reply-To: <430E5945.4000408@mediaroot.de>
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>

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?

-- 
Michael Fuhr



view thread (11+ messages)  latest in thread

Message-ID: <20050826013121.GA89046@winnie.fuhr.org>
Permalink:  ../20050826013121.GA89046@winnie.fuhr.org/
Also on:    postgresql.org/message-id/20050826013121.GA89046@winnie.fuhr.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: mike@fuhr.org, an@mediaroot.de, scrappy@postgresql.org
  Subject: Re: What is syslog:duration reporting ... ?
  In-Reply-To: <20050826013121.GA89046@winnie.fuhr.org>
  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>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox