Re: Planning time in explain/explain analyze - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Planning time in explain/explain analyze
Date
Msg-id 26398.1389329124@sss.pgh.pa.us
Whole thread Raw
In response to Re: Planning time in explain/explain analyze  (Greg Stark <stark@mit.edu>)
Responses Re: Planning time in explain/explain analyze
Re: Planning time in explain/explain analyze
List pgsql-hackers
Greg Stark <stark@mit.edu> writes:
> On Thu, Jan 9, 2014 at 9:14 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> In short then, I think we should just add this to EXPLAIN and be done.
>> -1 for sticking the info into PlannedStmt or anything like that.

> I'm confused. I thought I was arguing to support your suggestion that
> the initial planning store the time in the cached plan and explain
> should output the time the original planning took.

Uh, no, wasn't my suggestion.  Doesn't that design imply measuring *every*
planning cycle, explain or no?  I was thinking more of just putting the
timing calls into explain.c.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Bogus error handling in pg_upgrade
Next
From: Amit Kapila
Date:
Subject: Re: Standalone synchronous master