Re: Calculage avg. width when operator = is missing

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: Calculage avg. width when operator = is missing
Дата
Msg-id 20150922215654.GK295765@alvherre.pgsql
обсуждение исходный текст
Ответ на Re: Calculage avg. width when operator = is missing  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Calculage avg. width when operator = is missing  ("Shulgin, Oleksandr" <oleksandr.shulgin@zalando.de>)
Список 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 по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Calculage avg. width when operator = is missing
Следующее
От: Joe Conway
Дата:
Сообщение: Re: One question about security label command