| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Euler Taveira <euler(at)timbira(dot)com(dot)br>, Robert Haas <robertmhaas(at)gmail(dot)com>, Евгений Шишкин <itparanoia(at)gmail(dot)com>, 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 15:48:40 |
| Message-ID: | 55685.1463845720@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Sat, May 21, 2016 at 10:32 AM, Euler Taveira <euler(at)timbira(dot)com(dot)br>
> wrote:
>> I wouldn't like a command output controlled by GUC. EXPLAIN is used a
>> lot in bug/performance reports.
> And most of the time the choice of options is totally arbitrary based upon
> the mood and experience of the user, so what's it matter if they saved a
> few keystrokes and set the GUC in the .psqlrc file?
We've learned repeatedly that GUCs that affect command semantics are
dangerous. I do not think there's enough justification for that here.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Karlsson | 2016-05-21 17:01:56 | Re: Parallel safety tagging of extension functions |
| Previous Message | Tom Lane | 2016-05-21 15:45:38 | Re: Parallel safety tagging of extension functions |