| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Евгений Шишкин <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-20 23:34:45 |
| Message-ID: | CA+TgmoYZqbH4raR9p22Se8SCQCi5zJOH8Fpwuki0=AFy6Ddvpw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 19, 2016 at 6:24 PM, Евгений Шишкин <itparanoia(at)gmail(dot)com> wrote:
>> On 20 May 2016, at 01:12, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I'm a bit inclined to think that what this is really about is that we
>> made the wrong call on the BUFFERS option, and that it should default
>> to ON just like COSTS and TIMING do. Yeah, that would be an incompatible
>> change, but that's what major releases are for no?
>
> After thinking about it, i think this is a better idea.
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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-05-20 23:37:49 | Re: Parallel safety tagging of extension functions |
| Previous Message | David G. Johnston | 2016-05-20 20:41:51 | Re: Re: Request for Patch Feedback: Lag & Lead Window Functions Can Ignore Nulls |