On Thu, Mar 29, 2012 at 7:38 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> 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
> 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.
I don't know exactly how PL/Proxy or pgpool accomplish the multi-phase
aggregate, but in theory the proposal above is state-merge function,
so it doesn't apply to general aggregate results that passed through
the final function. Of course some functions that don't have final
functions are ok to call state-merge function on the results.
In response to
pgsql-hackers by date
|Next:||From: Dean Rasheed||Date: 2012-03-31 08:28:38|
|Subject: Tab completion of double quoted identifiers broken|
|Previous:||From: Robert Haas||Date: 2012-03-31 03:41:39|
|Subject: measuring lwlock-related latency spikes|