Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hT9aN-00045Q-Cd for pgsql-hackers@arkaria.postgresql.org; Tue, 21 May 2019 18:34:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hT9aL-0003X0-RS for pgsql-hackers@arkaria.postgresql.org; Tue, 21 May 2019 18:34:01 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hT9aL-0003Un-Eh for pgsql-hackers@lists.postgresql.org; Tue, 21 May 2019 18:34:01 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hT9aJ-0006qA-3I for pgsql-hackers@postgresql.org; Tue, 21 May 2019 18:34:00 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x4LIXoj1011849; Tue, 21 May 2019 14:33:50 -0400 From: Tom Lane To: Andres Freund cc: David Fetter , Robert Haas , Alvaro Herrera , Stephen Frost , PostgreSQL Development Subject: Re: New EXPLAIN option: ALL In-reply-to: <20190521181256.4gs5q3weldagc6el@alap3.anarazel.de> References: <20190515170529.GA18938@alvherre.pgsql> <11598.1557942806@sss.pgh.pa.us> <20190521173857.GH28936@fetter.org> <20190521181256.4gs5q3weldagc6el@alap3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Tue, 21 May 2019 11:12:56 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <11847.1558463630.1@sss.pgh.pa.us> Date: Tue, 21 May 2019 14:33:50 -0400 Message-ID: <11848.1558463630@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Andres Freund writes: > On 2019-05-21 19:38:57 +0200, David Fetter wrote: >> On Tue, May 21, 2019 at 12:32:21PM -0400, Robert Haas wrote: >>> Defaulting BUFFERS to ON is probably a reasonable change, thuogh. >> Would this be worth back-patching? I ask because adding it will cause >> fairly large (if mechanical) churn in the regression tests. > This is obviously a no. But I don't even know what large mechanical > churn you're talking about? There's not that many files with EXPLAIN > (ANALYZE) in the tests - we didn't have any until recently, when we > added SUMMARY OFF, to turn off non-deterministic details (f9b1a0dd4). partition_prune.sql has got kind of a lot of them though :-( src/test/regress/sql/tidscan.sql:3 src/test/regress/sql/partition_prune.sql:46 src/test/regress/sql/select_parallel.sql:3 src/test/regress/sql/select.sql:1 src/test/regress/sql/subselect.sql:1 Still, if we're adding BUFFERS OFF in the same places we have SUMMARY OFF, I agree that it won't create much new hazard for back-patching --- all those places already have a limit on how far they can be back-patched. regards, tom lane