Re: New EXPLAIN option: ALL - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: New EXPLAIN option: ALL
Date
Msg-id 41059d7a-2223-aa00-b8f6-9093676b2b34@2ndquadrant.com
Whole thread Raw
In response to Re: New EXPLAIN option: ALL  (David Fetter <david@fetter.org>)
Responses Re: New EXPLAIN option: ALL  (David Fetter <david@fetter.org>)
List 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@fetter.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



pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: progress report for ANALYZE
Next
From: Adam Berlin
Date:
Subject: Re: C testing for Postgres