From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | David Fetter <david(at)fetter(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: New EXPLAIN option: ALL |
Date: | 2019-07-02 14:06:52 |
Message-ID: | 41059d7a-2223-aa00-b8f6-9093676b2b34@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2019-05-18 19:39, David Fetter wrote:
> On Wed, May 15, 2019 at 09:32:31AM -0400, Tom Lane wrote:
>> David Fetter <david(at)fetter(dot)org> writes:
>>> I hope the patch is a little easier to digest as now attached.
>>
>> To be blunt, I find 500K worth of changes in the regression test
>> outputs to be absolutely unacceptable, especially when said changes
>> are basically worthless from a diagnostic standpoint. There are at
>> least two reasons why this won't fly:
>
> Here's a patch set with a much smaller change. Will that fly?
This appears to be the patch of record for this commit fest.
I don't sense much enthusiasm for this change. What is the exact
rationale for this proposal?
I think using a new keyword EXEC that is similar to an existing one
EXECUTE will likely just introduce a new class of confusion. (ANALYZE
EXEC EXECUTE ...?)
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Adam Berlin | 2019-07-02 14:10:51 | Re: C testing for Postgres |
Previous Message | Julien Rouhaud | 2019-07-02 13:22:42 | Re: progress report for ANALYZE |