Re: Materialized views WIP patch - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Materialized views WIP patch
Date
Msg-id 50AA7318.4000508@agliodbs.com
Whole thread Raw
In response to Re: Materialized views WIP patch  ("Kevin Grittner" <kgrittn@mail.com>)
Responses Re: Materialized views WIP patch  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
Kevin,

> I'm looking at whether there is some reasonable way to detect invalid
> data as well as capture age of data. Every solution I've thought of
> so far has at least one hard-to-solve race condition, but I have
> hopes that I can either solve that for one of the ideas, or come up
> with an idea which falls more gracefully under MVCC management.

What's the race condition?  I'd think that LOAD would take an exclusive
lock on the matview involved.

>   LOAD MATERIALIZED VIEW matview_name;
>
> to be very easy to confuse with
>
>   LOAD 'filename';
>
> But that's a subjective thing. If too many people find that
> confusing, it may be worth creating a new keyword; but I wanted to
> see whether it was really necessary first.

I do not find them confusing.

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY
Next
From: Josh Berkus
Date:
Subject: Re: Materialized views WIP patch