From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | salah jubeh <s_jubeh(at)yahoo(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Explain analyze time overhead |
Date: | 2013-12-10 21:59:44 |
Message-ID: | 20131210215944.GB14636@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Tue, Dec 10, 2013 at 01:53:54PM -0800, salah jubeh wrote:
> Thanks for the link, I find it very useful, unfortunatly I am using 9.1.11
> version.
>
> After digging a little bit, I find out that the gettimeofday is indeed a little
> bit slower on this particular machine than other machines, but it is not that
> significanat difference. The query I am running is not optimized, and for some
> reason the material operator is the one which causes most of the overhead. The
> whole issue is due to cross colums statistics and highly correlated predicates,
> the number of estimated records are much less than the actual number. Still, I
> did not understand completly, why the material operator consume about 9 minutes
> when I run explain analyze. i.e how many times we call gettimeofday for the
> material operator -I need to calculate this-? Finally, for testing purposes, I
> have disabled material and the query execution time dropped from 1 minute to
> 12 second.
The executable is not tied to any particular Postgres version, so you
could get the 9.3 binary and just use that.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
From | Date | Subject | |
---|---|---|---|
Next Message | Krzysztof Olszewski | 2013-12-10 23:30:48 | Problem with slow query with WHERE conditions with OR clause on primary keys |
Previous Message | salah jubeh | 2013-12-10 21:53:54 | Re: Explain analyze time overhead |