Re: pgsql: Move per-agg and per-trans duplicate finding to the planner.

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: pgsql: Move per-agg and per-trans duplicate finding to the planner.
Дата
Msg-id 20201124105853.GH3046@paquier.xyz
обсуждение исходный текст
Ответ на pgsql: Move per-agg and per-trans duplicate finding to the planner.  (Heikki Linnakangas <heikki.linnakangas@iki.fi>)
Ответы Re: pgsql: Move per-agg and per-trans duplicate finding to the planner.  (Heikki Linnakangas <hlinnaka@iki.fi>)
Список pgsql-committers
Hi Heikki,

On Tue, Nov 24, 2020 at 08:53:42AM +0000, Heikki Linnakangas wrote:
> Move per-agg and per-trans duplicate finding to the planner.
>
> This has the advantage that the cost estimates for aggregates can count
> the number of calls to transition and final functions correctly.
>
> Bump catalog version, because views can contain Aggrefs.
>
> Reviewed-by: Andres Freund
> Discussion: https://www.postgresql.org/message-id/b2e3536b-1dbc-8303-c97e-89cb0b4a9a48%40iki.fi

The regression tests of sepgsql are broken:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rhinoceros&dt=2020-11-24%2009%3A52%3A17

Reordering the lines in the output file would fix the issue.
--
Michael

Вложения

В списке pgsql-committers по дате отправления:

Предыдущее
От: Heikki Linnakangas
Дата:
Сообщение: pgsql: Move per-agg and per-trans duplicate finding to the planner.
Следующее
От: Heikki Linnakangas
Дата:
Сообщение: Re: pgsql: Move per-agg and per-trans duplicate finding to the planner.