Re: Support for REINDEX CONCURRENTLY - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Support for REINDEX CONCURRENTLY
Date
Msg-id 51BF0B2C.6080703@gmx.net
Whole thread Raw
In response to Re: Support for REINDEX CONCURRENTLY  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Support for REINDEX CONCURRENTLY  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On 6/17/13 8:23 AM, Michael Paquier wrote:
> As mentionned by Andres, the only thing that the MVCC catalog patch can
> improve here
> is the index swap phase (index_concurrent_swap:index.c) where the
> relfilenode of the
> old and new indexes are exchanged. Now an AccessExclusiveLock is taken
> on the 2 relations
> being swap, we could leverage that to ShareUpdateExclusiveLock with the
> MVCC catalog
> access I think.

Without getting rid of the AccessExclusiveLock, REINDEX CONCURRENTLY is
not really concurrent, at least not concurrent to the standard set by
CREATE and DROP INDEX CONCURRENTLY.




pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Batch API for After Triggers
Next
From: Kevin Grittner
Date:
Subject: Re: refresh materialized view concurrently