| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
| 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 16:02:42 |
| Message-ID: | 200310111602.h9BG2gN08641@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alvaro Herrera wrote:
> 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?
Which large statistics? Does he more than the default number of
statistics buckets?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2003-10-11 16:04:32 | Re: log_duration and \timing times repeatably much higher |
| Previous Message | Alvaro Herrera | 2003-10-11 15:52:56 | Re: log_duration and \timing times repeatably much higher |