pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chris Kratz <chris.kratz@vistashare.com>
To: pgsql-performance@postgresql.org
Subject: Large time difference between explain analyze and normal run
Date: Thu, 10 Feb 2005 13:34:40 -0500
Message-ID: <200502101334.40341.chris.kratz@vistashare.com> (raw)

Does anyone have any idea why there be over a 4s difference between running 
the statement directly and using explain analyze?  Multiple runs give the 
same result and I've tested on several servers.

db=# \timing
Timing is on.
db=# select count(*) from answer;
 count
--------
 530576
(1 row)

Time: 358.805 ms
db=# explain analyze select count(*) from answer;
                                                      QUERY PLAN
----------------------------------------------------------------------------------------------------------------------
 Aggregate  (cost=9848.12..9848.12 rows=1 width=0) (actual 
time=4841.231..4841.235 rows=1 loops=1)
   ->  Seq Scan on answer  (cost=0.00..8561.29 rows=514729 width=0) (actual 
time=0.011..2347.762 rows=530576 loops=1)
 Total runtime: 4841.412 ms
(3 rows)

Time: 4855.712 ms

---

Postgresql 7.4.5 running on Linux 2.6.8.1



view thread (5+ messages)  latest in thread

Message-ID: <200502101334.40341.chris.kratz@vistashare.com>
Permalink:  ../200502101334.40341.chris.kratz@vistashare.com/
Also on:    postgresql.org/message-id/200502101334.40341.chris.kratz@vistashare.com

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: chris.kratz@vistashare.com
  Subject: Re: Large time difference between explain analyze and normal run
  In-Reply-To: <200502101334.40341.chris.kratz@vistashare.com>

* 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