| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Amit Kapila <amit(dot)kapila(at)enterprisedb(dot)com> |
| Subject: | Combining Aggregates |
| Date: | 2014-12-17 09:53:13 |
| Message-ID: | CA+U5nMJ92azm0Yt8TT=hNxFP=VjFhDqFpaWfmj+66-4zvCGv3w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
KaiGai, David Rowley and myself have all made mention of various ways
we could optimize aggregates.
Following WIP patch adds an extra function called a "combining
function", that is intended to allow the user to specify a
semantically correct way of breaking down an aggregate into multiple
steps.
Gents, is this what you were thinking? If not...
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| aggregate_combining_fn.v1.patch | application/octet-stream | 39.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Atri Sharma | 2014-12-17 10:02:12 | Re: Combining Aggregates |
| Previous Message | Simon Riggs | 2014-12-17 09:49:52 | Re: pgaudit - an auditing extension for PostgreSQL |