Re: Identity projection

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Identity projection
Date: 2013-01-20 02:40:19
Message-ID: 20130120024019.GK16126@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kyotaro,

Are you planning to update this patch based on Heikki's comments? The
patch is listed in the commitfest and we're trying to make some
progress through all of those patches.

Thanks,

Stephen

* Heikki Linnakangas (hlinnaka(at)iki(dot)fi) wrote:
> On 12.11.2012 12:07, Kyotaro HORIGUCHI wrote:
> >Hello, This is new version of identity projection patch.
> >
> >Reverted projectionInfo and ExecBuildProjectionInfo. Identity
> >projection is recognized directly in ExecGroup, ExecResult, and
> >ExecWindowAgg. nodeAgg is reverted because I couldn't make it
> >sane..
> >
> >The following is the result of performance test posted before in
> >order to show the source of the gain.
>
> Hmm, this reminds me of the discussion on removing useless Limit
> nodes: http://archives.postgresql.org/pgsql-performance/2012-12/msg00127.php.
>
> The optimization on Group, WindowAgg and Agg nodes doesn't seem that
> important, the cost of doing the aggregation/grouping is likely
> overwhelming the projection cost, and usually you do projection in
> grouping/aggregation anyway. But makes sense for Result.
>
> For Result, I think you should aim to remove the useless Result node
> from the plan altogether. And do the same for useless Limit nodes.
>
> - Heikki
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2013-01-20 02:46:32 pg_upgrade and system() return value
Previous Message Andrew Dunstan 2013-01-19 23:15:39 Re: Strange Windows problem, lock_timeout test request