Re: Postgresql Materialized views

> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org [mailto:pgsql-hackers-
> owner(at)postgresql(dot)org] On Behalf Of Alvaro Herrera
> Sent: Monday, January 14, 2008 8:20 AM
> To: Mark Mielke
> Cc: Jean-Michel Pouré; pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] Postgresql Materialized views
>
> Mark Mielke wrote:
> > Alvaro Herrera wrote:
>
> >> But you had to modify your queries. I would think that a materialized
> >> views implementation worth its salt would put the view to work on the
> >> original, unmodified queries.
> >
> > I might be slow today (everyday? :-) ) - but what do you mean by this?
> The
> > only difference between *_table and *_view is that *_table is the
> summary
> > table and *_view is the view.
>
> 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.

Jon