Re: [BUGS] BUG #14889: explain analyze is taking much more time thanactual execution - Mailing list pgsql-bugs

From David Rowley
Subject Re: [BUGS] BUG #14889: explain analyze is taking much more time thanactual execution
Date
Msg-id CAKJS1f8ZmMFfr6MWzKAPo0GGLgT5Sbfo+GDcjKQguzcyzdDbDw@mail.gmail.com
Whole thread Raw
In response to [BUGS] BUG #14889: explain analyze is taking much more time than actualexecution  (mahmoud.alorfaly@gmail.com)
Responses Re: [BUGS] BUG #14889: explain analyze is taking much more time than actual execution  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On 6 November 2017 at 21:04, mahmoud alorfaly
<mahmoud.alorfaly@gmail.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


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: mahmoud alorfaly
Date:
Subject: Re: [BUGS] BUG #14889: explain analyze is taking much more time thanactual execution
Next
From: Alexander Korotkov
Date:
Subject: Fwd: [BUGS] pg_trgm word_similarity inconsistencies or bug