>
>> 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 upcomi
On Mon, May 19, 2014 at 6:47 AM, Tim Kane 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
On 05/18/2014 05:47 PM, Tim Kane wrote:
> Oh, I also noticed we don’t support alternate spellings of
> MATERIALIZE, as we do for ANALYZE.
> I’m not sure if we do this anywhere else, maybe it’s just analyze
> being the odd one out.
For the moment, if not forever, ANALYSE is the odd one out.
http:
HI all,
I’m curious about materialised views.
I was just setting something up, and noticed there is no support for
UNLOGGED materialised views
(http://www.postgresql.org/message-id/E1UZNrD-0008Eh-83@gemulon.postgresql.o
rg)
I also notice that the creation of an unlogged table appears to be a lot
