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

From Andreas Karlsson
Subject Re: Planning time in explain/explain analyze
Date
Msg-id 52D44B08.7060809@proxel.se
Whole thread Raw
In response to Re: Planning time in explain/explain analyze  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On 01/13/2014 09:06 PM, Stephen Frost wrote:
> My thought, at least, was to always grab the planning time and then
> provide it for explain and/or explain analyze, and then for re-plan
> cases, indicate if a cached plan was returned, if a replan happened, and
> if a replan happened, what the old plan time and the new plan time was.

I like this solution due it is correctness and that all information is 
included. But I also think my original path was fine in how it in its 
simplicity solved the problem without adding any overhead in the 
non-EXPLAIN case. Either solution would be fine by me. If the consensus 
is that we want to always measure it I will look at implementing that 
instead.

-- 
Andreas Karlsson



pgsql-hackers by date:

Previous
From: Claudio Freire
Date:
Subject: Re: Linux kernel impact on PostgreSQL performance
Next
From: Tom Lane
Date:
Subject: Re: Planning time in explain/explain analyze