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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: acamari(at)verlet(dot)org
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #7831: user defined-aggregated don't set initcond to null when unspecified, instead uses its first argument
Date: 2013-01-28 04:53:15
Message-ID: 18793.1359348795@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

acamari(at)verlet(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Abel Abraham Camarillo Ojeda 2013-01-28 05:10:49 Re: BUG #7831: user defined-aggregated don't set initcond to null when unspecified, instead uses its first argument
Previous Message acamari 2013-01-28 03:19:13 BUG #7831: user defined-aggregated don't set initcond to null when unspecified, instead uses its first argument