Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: BUG #7831: user defined-aggregated don't set initcond to null when unspecified, instead uses its first argument
Date
Msg-id 18793.1359348795@sss.pgh.pa.us
Whole thread Raw
In response to BUG #7831: user defined-aggregated don't set initcond to null when unspecified, instead uses its first argument  (acamari@verlet.org)
Responses Re: BUG #7831: user defined-aggregated don't set initcond to null when unspecified, instead uses its first argument
List pgsql-bugs
Tree view 
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 by date:

Previous
From: acamari@verlet.org
Date:
Subject: BUG #7831: user defined-aggregated don't set initcond to null when unspecified, instead uses its first argument
Next
From: Abel Abraham Camarillo Ojeda
Date:
Subject: Re: BUG #7831: user defined-aggregated don't set initcond to null when unspecified, instead uses its first argument