> On May 19, 2016, at 3:17 PM, Евгений Шишкин <itparan...@gmail.com> wrote:
>> On 19 May 2016, at 22:59, Tom Lane <t...@sss.pgh.pa.us> wrote:
>> David Christensen <da...@endpoint.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.
If it’s just a terminology issue, what about EXPLAIN (*); already a precedent
with SELECT * to mean “everything”. (MAX? LIKE_I’M_5?) Let the bikeshedding
In any case, I think a shorthand for “give me the most possible detail without
me having to lookup/type/remember the options” is a good tool.
End Point Corporation
Sent via pgsql-hackers mailing list (email@example.com)
To make changes to your subscription: