From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Fetter <david@fetter.org>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: PostgreSQL Development <pgsql-hackers@postgresql.org>
Subject: Re: New EXPLAIN option: ALL
Date: Tue, 21 May 2019 13:47:44 -0400
Message-ID: <17410.1558460864@sss.pgh.pa.us> (raw)
In-Reply-To: <20190521173857.GH28936@fetter.org>
References: <20190515170529.GA18938@alvherre.pgsql>
<11598.1557942806@sss.pgh.pa.us>
<CA+TgmoYxzEp1ejykNHJ95t1nJ8q63yPDeboi74GRzXceaJGMUw@mail.gmail.com>
<20190521173857.GH28936@fetter.org>
David Fetter <david@fetter.org> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, david@fetter.org, robertmhaas@gmail.com, alvherre@2ndquadrant.com, andres@anarazel.de, sfrost@snowman.net
Subject: Re: New EXPLAIN option: ALL
In-Reply-To: <17410.1558460864@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox