Re: GSoC - proposal - Materialized Views in PostgreSQL - Mailing list pgsql-hackers

From Robert Haas
Subject Re: GSoC - proposal - Materialized Views in PostgreSQL
Date
Msg-id g2t603c8f071004112000o6028510l3e97aeb58bb00bec@mail.gmail.com
Whole thread Raw
In response to Re: GSoC - proposal - Materialized Views in PostgreSQL  ("Florian G. Pflug" <fgp@phlo.org>)
List pgsql-hackers
On Sun, Apr 11, 2010 at 10:13 PM, Florian G. Pflug <fgp@phlo.org> wrote:
> If continuous updates prove to be too hard initially, you could instead
> update the view on select if it's outdated. Such a materialized view
> would be a kind of inter-session cache for subselects.
>
> The hard part would probably be to figure out how to decide whether the
> view is outdated or not, and to deal with two concurrent transactions
> trying to use an outdates view (and both trying to refresh it). What
> makes the second problem hard is that you wouldn't want one of the
> transactions to wait for the other to complete, because this is not how
> SELECTs traditionally behave.

Well, the proposed project is to create views that only get refreshed manually.

...Robert


pgsql-hackers by date:

Previous
From: "Florian G. Pflug"
Date:
Subject: Re: GSoC - proposal - Materialized Views in PostgreSQL
Next
From: Robert Haas
Date:
Subject: Re: GSoC - proposal - Materialized Views in PostgreSQL