Re: So why is EXPLAIN printing only *plan* time? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: So why is EXPLAIN printing only *plan* time?
Date
Msg-id CA+Tgmoao+QL1NsmBmTsBH-qfgwke1ehP4AEmMJnP7_XnGC4WkQ@mail.gmail.com
Whole thread Raw
In response to So why is EXPLAIN printing only *plan* time?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: So why is EXPLAIN printing only *plan* time?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, Apr 27, 2014 at 1:07 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> ... and not, in particular, parse analysis or rewrite time?

I think breaking those out would be a good idea.  Especially rewrite time.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Decrease MAX_BACKENDS to 2^16
Next
From: Andres Freund
Date:
Subject: Re: Decrease MAX_BACKENDS to 2^16