| From: | Michael Glaesemann <grzm(at)myrealbox(dot)com> |
|---|---|
| To: | David Pradier <dpradier(at)apartia(dot)fr> |
| Cc: | postgresql sql list <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: UPDATEABLE VIEWS ... Examples? |
| Date: | 2005-06-20 07:37:57 |
| Message-ID: | 3E0EA84A-7A3B-4BDC-ADB2-08D664551CD8@myrealbox.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Jun 20, 2005, at 4:16 PM, David Pradier wrote:
> This is maybe a newbie question, but what is the difference with a
> materialized view ?
As I understand it (and that understanding may be wrong) a
materialized view is a table that holds the values of a view from
some point in time. A view is a "saved" subselect. Everything you
call a view, the PostgreSQL backend re-evaluates the definition of
the view. A materialized view is only as accurate as the last time it
was updated. Things such as triggers can be used to keep the
materialized view updated. The key issue with materialized views is
to make sure it's always up-to-date with the evaluation of the view.
Michael Glaesemann
grzm myrealbox com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Pradier | 2005-06-20 07:56:31 | Re: UPDATEABLE VIEWS ... Examples? |
| Previous Message | David Pradier | 2005-06-20 07:27:55 | Re: UPDATEABLE VIEWS ... Examples? |