Andres Freund <and...@2ndquadrant.com> wrote: > if I understand things correctly REFRESH MATERIALIZED VIEW locks > the materialized view with an AcessExclusiveLock even if the view > already contains data.
Yeah. At the time I had to make a decision on that, REINDEX CONCURRENTLY did not seem reliable with a weaker lock, and REFRESH MATERIALIZED VIEW has to rebuild indexes (among other things). If we have all the issues sorted out with REINDEX CONCURRENTLY then the same techniques will probably apply to RMV without too much difficulty. It's a bit late to think about that for 9.3, though. > I am pretty sure that will - understandably - confuse users, so I > vote for at least including a note about that in the docs. Will see about working that in. -Kevin -- Kevin Grittner EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
