| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: using custom scan nodes to prototype parallel sequential scan |
| Date: | 2014-11-12 07:54:52 |
| Message-ID: | CAApHDvrydD0Wp89Y_TF4mx0+pWSdzomat3wWTpE-i_oEZEPyaA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Nov 11, 2014 at 9:29 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>
> This plan type is widely used in reporting queries, so will hit the
> mainline of BI applications and many Mat View creations.
> This will allow SELECT count(*) FROM foo to go faster also.
>
>
We'd also need to add some infrastructure to merge aggregate states
together for this to work properly. This means that could also work for
avg() and stddev etc. For max() and min() the merge functions would likely
just be the same as the transition functions.
Regards
David Rowley
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2014-11-12 07:57:27 | Re: group locking: incomplete patch, just for discussion |
| Previous Message | Michael Paquier | 2014-11-12 07:30:21 | New storage parameter pages_per_range not mentioned in CREATE INDEX doc |