Re: using custom scan nodes to prototype parallel sequential scan - Mailing list pgsql-hackers

From David Rowley
Subject Re: using custom scan nodes to prototype parallel sequential scan
Date
Msg-id CAApHDvrydD0Wp89Y_TF4mx0+pWSdzomat3wWTpE-i_oEZEPyaA@mail.gmail.com
Whole thread Raw
In response to Re: using custom scan nodes to prototype parallel sequential scan  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: using custom scan nodes to prototype parallel sequential scan  (Atri Sharma <atri.jiit@gmail.com>)
Re: using custom scan nodes to prototype parallel sequential scan  (Simon Riggs <simon@2ndQuadrant.com>)
Re: using custom scan nodes to prototype parallel sequential scan  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
On Tue, Nov 11, 2014 at 9:29 PM, Simon Riggs <simon@2ndquadrant.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

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: New storage parameter pages_per_range not mentioned in CREATE INDEX doc
Next
From: Jeff Davis
Date:
Subject: Re: group locking: incomplete patch, just for discussion