| From: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Greg Stark <gsstark(at)mit(dot)edu>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: log_duration and \timing times repeatably much higher |
| Date: | 2003-10-11 15:52:56 |
| Message-ID: | 20031011155256.GB2161@dcc.uchile.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Oct 11, 2003 at 11:22:36AM -0400, Bruce Momjian wrote:
> Martijn van Oosterhout wrote:
> -- Start of PGP signed section.
> > Planning time?
>
> Uh, I thought the actual number reported by EXPLAIN ANALYZE includes
> parse/plan times, but now that you mention it, if it is timing things
> inside the executor, it might be just executor times.
>
> Looking at explain.c, it is only timing the executor part in
> ExplainOnePlan(). The planner() call is outside that loop, so it must
> be parse/plan, though that seems like a lot of time spent in that area.
Could it be because of extremely large statistics settings for the
tables involved?
--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"Limítate a mirar... y algun día veras"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-10-11 16:02:42 | Re: log_duration and \timing times repeatably much higher |
| Previous Message | Bruce Momjian | 2003-10-11 15:22:36 | Re: log_duration and \timing times repeatably much higher |