On 2018-Aug-15, Robert Haas wrote: > On Tue, Aug 14, 2018 at 7:28 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > > I'm almost tempted to think that the reasons above make this a > > back-patchable bug fix. Comments? > > No objections to changing the behavior. Have you checked whether > there are any noticeable performance consequences? > > Back-patching seems a bit aggressive to me considering that the danger > is hypothetical.
That was my first thought too, and my preferred path would be to make this master-only and only consider a backpatch later if we find some practical reason to do so. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
