| From: | Andreas Karlsson <andreas(at)proxel(dot)se> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Planning time in explain/explain analyze |
| Date: | 2014-01-29 19:21:31 |
| Message-ID: | 52E954BB.1060404@proxel.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 01/28/2014 09:39 PM, Tom Lane wrote:
> I'm for doing the measurement in ExplainOneQuery() and not printing
> anything in code paths that don't go through there.
Reading the discussion here and realizing that my last patch was wrong I
am now in agreement with this. I have attached a patch which no longer
tries to measure planning time for prepared statements.
/Andreas
| Attachment | Content-Type | Size |
|---|---|---|
| explainplantime-v5.diff | text/x-patch | 16.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2014-01-29 19:21:46 | Re: pg_sleep_enhancements.patch |
| Previous Message | Christian Kruse | 2014-01-29 19:18:11 | Re: [PATCH] Use MAP_HUGETLB where supported (v3) |