| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Odd out of memory problem. |
| Date: | 2012-03-30 02:38:06 |
| Message-ID: | 1333075086.4554.31.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On tis, 2012-03-27 at 00:53 +0100, Greg Stark wrote:
> Hm. So my original plan was dependent on adding the state-merge
> function we've talked about in the past. Not all aggregate functions
> necessarily can support such a function but I think all or nearly all
> the builtin aggregates can. Certainly min,max, count, sum, avg,
> stddev, array_agg can which are most of what people do. That would be
> a function which can take two state variables and produce a new state
> variable.
This information could also be useful to have in PL/Proxy (or similar
FDWs) to be able to integrate aggregate computation into the language.
Currently, you always have to do the state merging yourself.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Farina | 2012-03-30 02:55:59 | Re: HTTP Frontend? (and a brief thought on materialized views) |
| Previous Message | Dobes Vandermeer | 2012-03-30 02:12:49 | Re: HTTP Frontend? (and a brief thought on materialized views) |