Re: BUG #7831: user defined-aggregated don't set initcond to null when unspecified, instead uses its first argument

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #7831: user defined-aggregated don't set initcond to null when unspecified, instead uses its first argument
Дата
Msg-id 18793.1359348795@sss.pgh.pa.us
обсуждение исходный текст
Ответ на BUG #7831: user defined-aggregated don't set initcond to null when unspecified, instead uses its first argument  (acamari@verlet.org)
Ответы Re: BUG #7831: user defined-aggregated don't set initcond to null when unspecified, instead uses its first argument  (Abel Abraham Camarillo Ojeda <acamari@verlet.org>)
Список pgsql-bugs
Дерево обсуждения 
acamari@verlet.org writes:
> user defined-aggregated don't set initcond to null when unspecified, instead
> uses its first argument.

And your point is?

AFAICS this is the documented behavior when the transition function
is strict.  See
http://www.postgresql.org/docs/9.1/static/sql-createaggregate.html
6th paragraph under "Description".

            regards, tom lane

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

Предыдущее
От: acamari@verlet.org
Дата:
Сообщение: BUG #7831: user defined-aggregated don't set initcond to null when unspecified, instead uses its first argument
Следующее
От: Abel Abraham Camarillo Ojeda
Дата:
Сообщение: Re: BUG #7831: user defined-aggregated don't set initcond to null when unspecified, instead uses its first argument