Re: Calculage avg. width when operator = is missing - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Calculage avg. width when operator = is missing
Date
Msg-id 20150922215654.GK295765@alvherre.pgsql
Whole thread Raw
In response to Re: Calculage avg. width when operator = is missing  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Calculage avg. width when operator = is missing  ("Shulgin, Oleksandr" <oleksandr.shulgin@zalando.de>)
List pgsql-hackers
Tom Lane wrote:

> Should we consider this HEAD-only, or a back-patchable bug fix?
> Or perhaps compromise on HEAD + 9.5?

It looks like a bug to me, but I think it might destabilize approved
execution plans(*), so it may not be such a great idea to back patch
branches that are already released.  I think HEAD + 9.5 is good.

(*) I hear there are even applications where queries and their approved
execution plans are kept in a manifest, and plans that deviate from that
raise all kinds of alarms.  I have never seen such a thing ...

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Calculage avg. width when operator = is missing
Next
From: Joe Conway
Date:
Subject: Re: One question about security label command