Re: Incorrect Total runtime Reported by Explain Analyze!?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.


[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux