| From: | David Fetter <david(at)fetter(dot)org> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: tuplestore, tuplesort aggregate functions |
| Date: | 2010-08-18 14:24:52 |
| Message-ID: | 20100818142452.GB15385@fetter.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 18, 2010 at 04:10:18PM +0200, Pavel Stehule wrote:
> 2010/8/18 David Fetter <david(at)fetter(dot)org>:
> > Which median do you plan to implement? Or do you plan to implement
> > several different medians, each with distinguishing names?
>
> my proposal enabled implementation of any "median like" function. But
> if we implement median as special case of aggregate, then some basic
> "median" will be implemented.
Apart from the medians, which "median-like" aggregates do you have in
mind to start with? If you can provide examples of "median-like"
aggregates that people might need to implement as user-defined
aggregates, or other places where people would use this machinery, it
will make your case stronger for this refactoring.
Otherwise, it seems like a more reasonable thing to make the medians
special case code.
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-08-18 14:39:33 | Re: proposal: tuplestore, tuplesort aggregate functions |
| Previous Message | Pavel Stehule | 2010-08-18 14:10:18 | Re: proposal: tuplestore, tuplesort aggregate functions |