| From: | Евгений Шишкин <itparanoia(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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-19 20:17:12 |
| Message-ID: | A35D17A1-25AF-4007-9178-6F689A1BCE2A@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 19 May 2016, at 22:59, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> David Christensen <david(at)endpoint(dot)com> writes:
>> This simple patch adds “ALL” as an EXPLAIN option as shorthand for “EXPLAIN (ANALYZE, VERBOSE, COSTS, TIMING, BUFFERS)” for usability.
>
> I'm not sure this is well thought out. It would mean for example that
> we could never implement EXPLAIN options that are mutually exclusive
> ... at least, not without having to redefine ALL as all-except-something.
> Non-boolean options would be problematic as well.
>
Maybe EVERYTHING would be ok.
But it is kinda long word to type.
> regards, tom lane
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-05-19 20:26:22 | Re: [PATCH] Add EXPLAIN (ALL) shorthand |
| Previous Message | Michael Paquier | 2016-05-19 20:14:48 | Tracking wait event for latches |