| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: array functions - request for opinions (was Re: [PATCHES] array |
| Date: | 2003-05-25 23:19:48 |
| Message-ID: | Pine.LNX.4.44.0305260115110.1897-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Joe Conway writes:
> >>And in any case, array_accum() is intended to be used for building
> >>custom aggregates, so that needs to be documented.
> > Can you give an example of an aggregate or a class of aggregates where
> > this would be useful?
> There are many discussions on the lists over the past few years in which
> people have requested this kind of functionality. There is even a
> contrib/intagg that does this for integers only. I don't think there is
> any question that there is a demand for the feature. Some examples:
These applications should use an empty array as initial value. Then the
normal array concatenation can be used as transition function.
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-05-26 00:35:21 | Re: Domain breakage |
| Previous Message | Michael Brusser | 2003-05-25 22:55:38 | Re: vacuum analyze corrupts database |