Re: materialised views vs unlogged table (also, ize vs ise)

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Tim Kane <tim(dot)kane(at)gmail(dot)com>
Cc: pgsql-general General <pgsql-general(at)postgresql(dot)org>
Subject: Re: materialised views vs unlogged table (also, ize vs ise)
Date: 2014-05-19 00:07:09
Message-ID: CAB7nPqSLJtTLdhijobvwCMf7K4G-EKuiUPyx5t+3aPQdYFg=iw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, May 19, 2014 at 6:47 AM, Tim Kane <tim(dot)kane(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2014-05-19 00:59:38 Re: How to solve the problem "error reading c:\Program Files\PostgreSQL\9.3\data\postgresql.conf during installation"
Previous Message Dean Rasheed 2014-05-18 23:10:53 Re: 9.4 beta - pg_get_viewdef() and WITH CHECK OPTION