Re: UPDATEABLE VIEWS ... Examples? - Mailing list pgsql-sql

From Michael Glaesemann
Subject Re: UPDATEABLE VIEWS ... Examples?
Date
Msg-id 3E0EA84A-7A3B-4BDC-ADB2-08D664551CD8@myrealbox.com
Whole thread Raw
In response to Re: UPDATEABLE VIEWS ... Examples?  (David Pradier <dpradier@apartia.fr>)
Responses Re: UPDATEABLE VIEWS ... Examples?  (David Pradier <dpradier@apartia.fr>)
List 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




pgsql-sql by date:

Previous
From: David Pradier
Date:
Subject: Re: UPDATEABLE VIEWS ... Examples?
Next
From: David Pradier
Date:
Subject: Re: UPDATEABLE VIEWS ... Examples?