Re: materialised views vs unlogged table (also, ize vs ise) - Mailing list pgsql-general

From Michael Paquier
Subject Re: materialised views vs unlogged table (also, ize vs ise)
Date
Msg-id CAB7nPqSLJtTLdhijobvwCMf7K4G-EKuiUPyx5t+3aPQdYFg=iw@mail.gmail.com
Whole thread Raw
In response to materialised views vs unlogged table (also, ize vs ise)  (Tim Kane <tim.kane@gmail.com>)
Responses Re: materialised views vs unlogged table (also, ize vs ise)
List pgsql-general
On Mon, May 19, 2014 at 6:47 AM, Tim Kane <tim.kane@gmail.com> wrote:
> Aside from the convenience of the REFRESH functionality, are there any other
> factors I should consider?
An exclusive lock is taken on the materialized view during a REFRESH
operation, blocking an read or write queries attempted on them. You
can tackle this limitation in the upcoming 9.4 by using REFRESH
CONCURRENTLY, a unique index being necessary on the materialized view.
--
Michael


pgsql-general by date:

Previous
From: Dean Rasheed
Date:
Subject: Re: 9.4 beta - pg_get_viewdef() and WITH CHECK OPTION
Next
From: Adrian Klaver
Date:
Subject: Re: How to solve the problem "error reading c:\Program Files\PostgreSQL\9.3\data\postgresql.conf during installation"