Re: MAX/MIN optimization via rewrite (plus query - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: MAX/MIN optimization via rewrite (plus query
Date
Msg-id 20041112202547.GC77327@decibel.org
Whole thread Raw
In response to Re: MAX/MIN optimization via rewrite (plus query  (Bruno Wolff III <bruno@wolff.to>)
List pgsql-hackers
On Thu, Nov 11, 2004 at 11:59:06AM -0600, Bruno Wolff III wrote:
> On Thu, Nov 11, 2004 at 09:29:14 +0000,
>   Simon Riggs <simon@2ndquadrant.com> wrote:
> > On Wed, 2004-11-10 at 22:48, Mark Kirkwood wrote:
> > > Planning for future note: I would like whatever mechanism that is added 
> > > for this MAX/MIN stuff to be amenable to more subtle things like 
> > > aggregate navigation (see R.Kimball's article 
> > > http://www.dbmsmag.com/9608d54.html).
> > > 
> > 
> > With you on that one...
> 
> I disaggree. What that author is suggesting is orthogonal to what is being
> proposed by Mark. That article is really suggesting a varient of materialized
> views where you can use the normal aggregate notation instead of having
> to use a special column name to get access to an aggregate in the
> materialized view.

And it also appears to be completely missing the automatic query rewrite
capabilites found in Oracle, DB2, and MSSQL.
-- 
Jim C. Nasby, Database Consultant               decibel@decibel.org 
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"


pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: MAX/MIN optimization via rewrite (plus query rewrites generally)
Next
From: Oleg Bartunov
Date:
Subject: 8.0 press release