Re: Missing optimization when filters are applied after window functions - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Missing optimization when filters are applied after window functions
Date
Msg-id 20120524195521.GI10306@momjian.us
Whole thread Raw
In response to Re: Missing optimization when filters are applied after window functions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, May 16, 2012 at 09:25:13AM -0400, Tom Lane wrote:
> Volker Grabsch <vog@notjusthosting.com> writes:
> > I propose the following general optimization: If all window
> > functions are partitioned by the same first field (here: id),
> > then any filter on that field should be executed before
> > WindowAgg.
> 
> I'm not sure if that rule is correct in detail, but in any case the
> short answer is that window aggregates are a new feature in Postgres
> and we basically haven't done any optimization work on them yet.
> Feel free to work in that area if it interests you...

Is this a TODO?

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Backends stalled in 'startup' state: index corruption
Next
From: Robert Haas
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Send new protocol keepalive messages to standby servers.