X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 8983E9DCA00 for ; Thu, 26 Jan 2006 12:35:48 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 49855-08 for ; Thu, 26 Jan 2006 12:35:46 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id DA7E49DC809 for ; Thu, 26 Jan 2006 12:35:45 -0400 (AST) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Thu, 26 Jan 2006 16:35:43 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 26 Jan 2006 10:35:43 -0600 Subject: Re: Incorrect Total runtime Reported by Explain Analyze!? From: Scott Marlowe To: Jozsef Szalay Cc: pgsql-performance@postgresql.org In-Reply-To: References: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Message-Id: <1138293343.22740.5.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Thu, 26 Jan 2006 10:35:43 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.295 required=5 tests=[AWL=-0.032, PLING_QUERY=0.326, UNPARSEABLE_RELAY=0.001] X-Spam-Score: 0.295 X-Spam-Level: X-Archive-Number: 200601/443 X-Sequence-Number: 16921 On Thu, 2006-01-26 at 09:50, Jozsef Szalay wrote: > Hi All, >=20 > =20 >=20 > 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=E2=80=99m 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've seen this problem before in 7.4 and 8.0 as well.