Re: So why is EXPLAIN printing only *plan* time?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: So why is EXPLAIN printing only *plan* time?
Date: 2014-04-28 11:33:04
Message-ID: CA+Tgmoao+QL1NsmBmTsBH-qfgwke1ehP4AEmMJnP7_XnGC4WkQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Apr 27, 2014 at 1:07 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-04-28 11:37:01 Re: Decrease MAX_BACKENDS to 2^16
Previous Message Heikki Linnakangas 2014-04-28 10:32:45 Re: Decrease MAX_BACKENDS to 2^16