Re: possible optimization: push down aggregates - Mailing list pgsql-hackers

From Claudio Freire
Subject Re: possible optimization: push down aggregates
Date
Msg-id CAGTBQpZ0Op_r6e_1Pci9fMf-ksgMAeL6wu_q_ob2vKGNGj7aXg@mail.gmail.com
Whole thread Raw
In response to Re: possible optimization: push down aggregates  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
On Wed, Aug 27, 2014 at 6:46 PM, Merlin Moncure <mmoncure@gmail.com> wrote:
>
> Yeah: I was overthinking it.   My mind was on parallel processing of
> the aggregate (which is not what Pavel was proposing) because that
> just happens to be what I'm working on currently -- using dblink to
> decompose various aggregates and distribute the calculation across
> servers.  "Woudn't it nice to have to the server to that itself", I
> impulsively thought.

But you'd have part of it too. Because then you'd have semantically
independent parallel nodes in the plan that do some meaningful data
wrangling and spit little output, whereas the previous plan did not do
much with the data and spit loads of rows as a result. This is a big
previous step for parallel execution really.



pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: possible optimization: push down aggregates
Next
From: Julien Rouhaud
Date:
Subject: Re: [TODO] Track number of files ready to be archived in pg_stat_archiver