From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Can I use PostgreSQL to develop a self-organizing |
Date: | 2003-09-08 21:55:43 |
Message-ID: | 873cf754io.fsf@stark.dyndns.tv |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> writes:
> On Mon, 2003-09-08 at 15:22, Karsten Hilbert wrote:
>
> > I also use views to simplify application code by moving
> > complicated queries onto the backend. I wonder what, if any,
>
> Are you referring to Access' tendency to do the joins on the client?
No, I think he doesn't mean move execution to the backend, just lexically
hoisting the complex repeated code out of the front-end code.
A self-organizing materialized view system might be able to use normal
non-materialized views as hints to help it find useful views to materialize.
It also might help the programmer avoid implementing functionally equivalent
but non-identical forms of the same view in different queries, defeating the
automated recognition of similar views.
Materialized views are a godsend for DSS systems, and self-organized
materialized views sound too good to be true. Is this really feasible?
It sounds awfully ambitious considering postgres doesn't even have
materialized views yet.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-09-08 21:58:09 | Re: ISO 8601 'Time Intervals' of the 'format with time-unit |
Previous Message | Tom Lane | 2003-09-08 21:47:48 | Re: why does count take so long? |