Re: REINDEX CONCURRENTLY 2.0 - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: REINDEX CONCURRENTLY 2.0
Date
Msg-id 5465215D.2060505@gmx.net
Whole thread Raw
In response to Re: REINDEX CONCURRENTLY 2.0  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: REINDEX CONCURRENTLY 2.0  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On 11/12/14 7:31 PM, Andres Freund wrote:
> Yes, it sucks. But it beats not being able to reindex a relation with a
> primary key (referenced by a fkey) without waiting several hours by a
> couple magnitudes. And that's the current situation.

That's fine, but we have, for better or worse, defined CONCURRENTLY :=
does not take exclusive locks.  Use a different adverb for an in-between
facility.




pgsql-hackers by date:

Previous
From: Antonin Houska
Date:
Subject: Re: array exclusion constraints
Next
From: Robert Haas
Date:
Subject: Re: tracking commit timestamps