| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: refresh materialized view concurrently |
| Date: | 2013-06-17 18:57:18 |
| Message-ID: | 51BF5C0E.3090400@agliodbs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2013-06-17 19:52:36 | Re: Support for REINDEX CONCURRENTLY |
| Previous Message | Josh Berkus | 2013-06-17 18:53:54 | Re: [RFC] Minmax indexes |