Re: GSoC - Materialized Views - is stale or fresh?

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Magnus Hagander" <magnus(at)hagander(dot)net>
Cc: "Greg Smith" <greg(at)2ndquadrant(dot)com>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>, "Pavel Baros" <baros(dot)p(at)seznam(dot)cz>
Subject: Re: GSoC - Materialized Views - is stale or fresh?
Date: 2010-06-14 15:17:55
Message-ID: 4C1601D30200002500032296@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> What Pavel's trying to do here is be smart about figuring out when
> an MV needs to be refreshed. I'm pretty sure this is the wrong
> way to go about it, but it seems entirely premature considering
> that we don't have a working implementation of a *manually*
> refreshed MV.

Agreed all around.

At the risk of sounding obsessed, this is an area where predicate
locks might be usefully extended, if and when the serializable patch
makes it in.

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2010-06-14 15:19:16 Re: Re: [PERFORM] Large (almost 50%!) performance drop after upgrading to 8.4.4?
Previous Message Robert Haas 2010-06-14 15:14:38 Re: warning message in standby