Re: BUG #14889: explain analyze is taking much more time than actual execution

From: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
To: mahmoud alorfaly <mahmoud(dot)alorfaly(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14889: explain analyze is taking much more time than actual execution
Date: 2017-11-06 08:08:59
Message-ID: CAKJS1f8ZmMFfr6MWzKAPo0GGLgT5Sbfo+GDcjKQguzcyzdDbDw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 6 November 2017 at 21:04, mahmoud alorfaly
<mahmoud(dot)alorfaly(at)gmail(dot)com> wrote:
> With EXPLAIN (ANALYZE, TIMING OFF), it is back to normal execution speed.

Then it's just the TIMING overhead that's causing the slowdown. This
will vary depending on how long gettimeofday() takes on your system.

This is known to be an overhead which is one of the reasons the TIMING
OFF option exists.

--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexander Korotkov 2017-11-06 11:34:24 Fwd: pg_trgm word_similarity inconsistencies or bug
Previous Message mahmoud alorfaly 2017-11-06 08:04:10 Re: BUG #14889: explain analyze is taking much more time than actual execution