Re: using custom scan nodes to prototype parallel sequential scan

From: Kouhei Kaigai <kaigai(at)ak(dot)jp(dot)nec(dot)com>
To: David Rowley <dgrowley(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, 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-18 04:57:57
Message-ID: 9A28C8860F777E439AA12E8AEA7694F801078DED@BPXM15GP.gisp.nec.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 18 November 2014 05:19, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>
>
> On 14 November 2014 11:02, Kouhei Kaigai <kaigai(at)ak(dot)jp(dot)nec(dot)com>
> wrote:
>
> > I'd like to throw community folks a question.
> > Did someone have a discussion to the challenge of aggregate
> push-down across
> > relations join in the past? It potentially reduces number of rows
> to be joined.
> > If we already had, I'd like to check up the discussion at that
> time.
>
> Yes, I was looking at aggregate pushdown. I think it needs the same
> changes to aggregates discussed upthread.
>
>
>
>
> I have something that I've been working on locally. It's far from ready,
> but it does work in very simple cases, and shows a nice performance boost.
> I'll start another thread soon and copy you both in. Perhaps we can share
> some ideas.
>
Great, it's exactly valuable functionality to be in the core.

--
NEC OSS Promotion Center / PG-Strom Project
KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2014-11-18 06:20:50 Re: [TODO] Track number of files ready to be archived in pg_stat_archiver
Previous Message Pavel Stehule 2014-11-18 04:37:24 Re: proposal: plpgsql - Assert statement