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

2013-01-27 Thread acamari
The following bug has been logged on the website: Bug reference: 7831 Logged by: Abel Abraham Camarillo Ojeda Email address: acam...@verlet.org PostgreSQL version: 9.1.2 Operating system: OpenBSD-5.1/amd64.MP Description: user defined-aggregated don't set initcond to

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

2013-01-27 Thread Tom Lane
acam...@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

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

2013-01-27 Thread Abel Abraham Camarillo Ojeda
On Sun, Jan 27, 2013 at 10:53 PM, Tom Lane wrote: > acam...@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. Se