Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> Maybe I am missing something here, but reindex concurrently should do
> 1) BEGIN
> 2) Lock table in share update exlusive
> 3) lock old index
> 3) create new index
> 4) obtain session locks on table, old index, new index
> 5) commit
> 6) process till newindex->insisready (no new locks)
> 7) process till newindex->indisvalid (no new locks)
> 8) process till !oldindex->indisvalid (no new locks)
> 9) process till !oldindex->indisready (no new locks)
> 10) drop all session locks
> 11) lock old index exlusively which should be "invisible" now
> 12) drop old index

You can't drop the session locks until you're done.  Consider somebody
else trying to do a DROP TABLE between steps 10 and 11, for instance.

			regards, tom lane

In response to

• Re: Support for REINDEX CONCURRENTLY at 2012-10-03 11:08:24 from Andres Freund

Responses

• Re: Support for REINDEX CONCURRENTLY at 2012-10-03 14:52:17 from Andres Freund

pgsql-hackers by date

Next:	From: Alvaro Herrera	Date: 2012-10-03 14:38:57
	Subject: Re: [9.1] 2 bugs with extensions
Previous:	From: Fabrízio de Royes Mello	Date: 2012-10-03 13:11:03
	Subject: Re: CREATE SCHEMA IF NOT EXISTS