Re: Materialized views WIP patch

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Kevin Grittner <kgrittn(at)mail(dot)com>
Cc: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Materialized views WIP patch
Date: 2012-11-19 17:57:44
Message-ID: 50AA7318.4000508@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2012-11-19 18:01:51 Re: Materialized views WIP patch
Previous Message Tom Lane 2012-11-19 17:54:55 Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY