Re: multi-column aggregates

From: Berend Tober <btober(at)seaworthysys(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: multi-column aggregates
Date: 2006-03-13 20:36:28
Message-ID: 4415D7CC.4040601@seaworthysys.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane wrote:

>Chris Kratz <chris(dot)kratz(at)vistashare(dot)com> writes:
>
>
>>Thanks for the reply. Yes, subselects would work very well and in some ways
>>are more elegant then the hand waving we had to do to get the multi-column
>>aggregates to work.
>>
>>
>
>BTW, there is not any fundamental reason why we can't support aggregate
>functions with multiple inputs. I looked at this not long ago and
>determined that the major stumbling blocks would be
>(1) trying to keep the code in nodeAgg.c from getting a lot more
>complicated and hence slower for the single-input case;
>(2) figuring out how to change the syntax for CREATE AGGREGATE.
>
>It certainly seems doable if someone wants to spend time on it.
>
>
I did some work a couple months ago (and posted here
"http://archives.postgresql.org/pgsql-general/2005-11/msg01214.php") on
developing composite aggregates for linear-regression, and while at first I was a bit dissatisfied with having to cast my data pairs as POINT data type, once I got confortable with that it made a lot of sense.

Regards,
Berend Tober

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Chris Kratz 2006-03-13 20:45:55 Re: multi-column aggregates
Previous Message Tom Lane 2006-03-13 20:28:13 Re: ERROR: FULL JOIN is only supported with merge-joinable