From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Combining Aggregates |
Date: | 2015-02-24 19:20:32 |
Message-ID: | 54ECCF00.9080906@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2/20/15 3:09 PM, Tomas Vondra wrote:
> The 'combine' function gets two such 'state' values, while transition
> gets 'state' + next value.
I think the combine function is not actually a property of the
aggregate, but a property of the transition function. If two aggregates
have the same transition function, they will also have the same combine
function. The combine function really just says, how do you combine two
series of these function calls. Say maybe this should be put into
pg_proc instead. (Or you make the transition functions transition
operators and put the info into pg_operator instead, which is where
function call optimization information is usually kept.)
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2015-02-24 19:27:10 | Re: Enforce creation of destination folders for source files in pg_regress (Was: pg_regress writes into source tree) |
Previous Message | Gord Tomlin | 2015-02-24 19:17:00 | Re: PostgreSQL on z/OS UNIX? |