Re: Incorrect Total runtime Reported by Explain Analyze!? - Mailing list pgsql-performance

From Scott Marlowe
Subject Re: Incorrect Total runtime Reported by Explain Analyze!?
Date
Msg-id 1138298389.22740.11.camel@state.g2switchworks.com
Whole thread Raw
In response to Re: Incorrect Total runtime Reported by Explain Analyze!?  (Michael Fuhr <mike@fuhr.org>)
List pgsql-performance
On Thu, 2006-01-26 at 11:57, Michael Fuhr wrote:
> On Thu, Jan 26, 2006 at 04:49:59PM +0000, Richard Huxton wrote:
> > Jozsef Szalay wrote:
> > >I have seen it on occasion that the total runtime reported by explain
> > >analyze was much higher than the actual time the query needed to
> > >complete. The differences in my case ranged between 20-120 seconds. I'm
> > >just curious if anyone else has experienced this and whether there is
> > >something that I can do to convince explain analyze to report the
> > >execution time of the query itself rather than the time of its own
> > >execution. Engine version is 8.1.1.
> >
> > I think it's down to all the gettime() calls that have to be made to
> > measure how long each stage of the query takes. In some cases these can
> > take a substantial part of the overall query time.
>
> Another possibility is that the total query time was indeed that
> long because the query was blocked waiting for a lock.  For example:

Could be, but I've had this happen where the query returned in like 1
second but reported 30 seconds run time.

pgsql-performance by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: Incorrect Total runtime Reported by Explain Analyze!?
Next
From: "Jozsef Szalay"
Date:
Subject: Re: Incorrect Total runtime Reported by Explain Analyze!?