Re: refresh materialized view concurrently - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: refresh materialized view concurrently
Date
Msg-id 51BF5C0E.3090400@agliodbs.com
Whole thread Raw
In response to refresh materialized view concurrently  (Kevin Grittner <kgrittn@ymail.com>)
List pgsql-hackers
On 06/17/2013 04:13 AM, Heikki Linnakangas wrote:
> On 14.06.2013 19:05, Kevin Grittner wrote:
>> Attached is a patch for REFRESH MATERIALIZED VIEW CONCURRENTLY for
>> 9.4 CF1.  The goal of this patch is to allow a refresh without
>> interfering with concurrent reads, using transactional semantics.
>>
>> It is my hope to get this committed during this CF to allow me to
>> focus on incremental maintenance for the rest of the release cycle.
> 
> I must say this seems a bit pointless on its own. But if it's a stepping
> stone to incremental maintenance, I have no objections.

Actually, CONCURRENTLY was cited as the #1 deficiency for the matview
feature for 9.3.  With it, the use-case for Postgres matviews is
broadened considerably.  So it's very valuable on its own, even if (for
example) INCREMENTAL didn't get done for 9.3.

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



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: [RFC] Minmax indexes
Next
From: Josh Berkus
Date:
Subject: Re: Support for REINDEX CONCURRENTLY