On Tue, Jul 2, 2013 at 4:02 AM, Hitoshi Harada <umi.tanuki@gmail.com> wrote:
> Other than these, I've found index is opened with NoLock, relying on
> ExclusiveLock of parent matview, and ALTER INDEX SET TABLESPACE or something
> similar can run concurrently, but it is presumably safe. DROP INDEX,
> REINDEX would be blocked by the ExclusiveLock.
I doubt very much that this is safe. And even if it is safe today, I
think it's a bad idea, because we're likely to try to reduce lock
levels in the future. Taking no lock on a relation we're opening,
even an index, seems certain to be a bad idea.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company