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 1hT8rl-0001oO-Qu for pgsql-hackers@arkaria.postgresql.org; Tue, 21 May 2019 17:47:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hT8rk-0006GS-F4 for pgsql-hackers@arkaria.postgresql.org; Tue, 21 May 2019 17:47:56 +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 1hT8rk-0006GL-3A for pgsql-hackers@lists.postgresql.org; Tue, 21 May 2019 17:47:56 +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 1hT8rh-0005oC-SW for pgsql-hackers@postgresql.org; Tue, 21 May 2019 17:47:54 +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 x4LHlich017411; Tue, 21 May 2019 13:47:44 -0400 From: Tom Lane To: David Fetter cc: Robert Haas , Alvaro Herrera , Andres Freund , Stephen Frost , PostgreSQL Development Subject: Re: New EXPLAIN option: ALL In-reply-to: <20190521173857.GH28936@fetter.org> References: <20190515170529.GA18938@alvherre.pgsql> <11598.1557942806@sss.pgh.pa.us> <20190521173857.GH28936@fetter.org> Comments: In-reply-to David Fetter message dated "Tue, 21 May 2019 19:38:57 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <17409.1558460864.1@sss.pgh.pa.us> Date: Tue, 21 May 2019 13:47:44 -0400 Message-ID: <17410.1558460864@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk David Fetter writes: > 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. It really doesn't matter how much churn it causes in the regression tests. Back-patching a significant non-bug behavioral change like that is exactly the kind of thing we don't do, because it will cause our users pain. regards, tom lane