| From: | Euler Taveira <euler(at)timbira(dot)com(dot)br> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Евгений Шишкин <itparanoia(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Christensen <david(at)endpoint(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Add EXPLAIN (ALL) shorthand |
| Date: | 2016-05-21 14:32:07 |
| Message-ID: | 57407167.5000406@timbira.com.br |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 20-05-2016 20:34, Robert Haas wrote:
> Hmm, my experience is different. I use EXPLAIN (ANALYZE, VERBOSE) a
> lot, but EXPLAIN (ANALYZE, BUFFERS) only rarely. I wonder if a GUC is
> the way to go.
>
I wouldn't like a command output controlled by GUC. EXPLAIN is used a
lot in bug/performance reports. I'm predicting users that will have
trouble while using EXPLAIN if someone change the suggested GUC. It also
breaks clients/applications that parse EXPLAIN. I don't want another
bytea_output. However, if someone wants to suggest turning on/off some
option defaults, I'm all ears.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2016-05-21 15:06:14 | Re: [PATCH] Add EXPLAIN (ALL) shorthand |
| Previous Message | Tom Lane | 2016-05-21 14:12:41 | Re: Does "explain (QueryTree [RAW| ANAYLZE|REWRITE] | Optimization [PULL_UP_BEFORE| PULL_UP_AFTER|...]) SELECT XXXX" helpful? |