From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com> |
Cc: | 'Alvaro Herrera' <alvherre(at)commandprompt(dot)com>, Mark Mielke <mark(at)mark(dot)mielke(dot)cc>, Jean-Michel Pouré <jm(at)poure(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Postgresql Materialized views |
Date: | 2008-01-14 14:47:23 |
Message-ID: | 20080114144723.GC11559@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jan 14, 2008 at 08:30:53AM -0600, Roberts, Jon wrote:
> > My point is that you should be able to query _table and the system
> > should automatically use the view, without you saying so (except by
> > initially creating them).
> >
> I agree! From a BI perspective, a materialized view is worthless if you
> have to re-write your query. There isn't a tool on the market that is smart
> enough to rewrite a query to a view because all other databases handle the
> rewriting internally.
I don't know about worthless, given that people are doing materialised
views on postgres already. It is however a completely orthoginal
problem. Someone needs to write the code to maintain such a view before
you can even think about working on the planner.
However, step 1 would be to get them onto the TODO list.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Those who make peaceful revolution impossible will make violent revolution inevitable.
> -- John F Kennedy
From | Date | Subject | |
---|---|---|---|
Next Message | Zeugswetter Andreas ADI SD | 2008-01-14 14:50:33 | Re: Postgresql Materialized views |
Previous Message | Andrew Dunstan | 2008-01-14 14:38:52 | Re: Postgresql Materialized views |