Re: Should I implement DROP INDEX CONCURRENTLY? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Should I implement DROP INDEX CONCURRENTLY?
Date
Msg-id 1326740778.29466.10.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: Should I implement DROP INDEX CONCURRENTLY?  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Should I implement DROP INDEX CONCURRENTLY?  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On mån, 2012-01-16 at 11:17 -0500, Robert Haas wrote:
> I don't see how setting indisvalid to false helps with this, because
> IIUC when a session sees indisvalid = false, it is supposed to avoid
> using the index for queries but still make new index entries when a
> write operation happens - but to drop an index, I think you'd need to
> get into a state where no one was using the index for anything at all.

ISTM that one would need to set indisready to false instead.




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: pg_basebackup option for handling symlinks
Next
From: Heikki Linnakangas
Date:
Subject: Re: foreign key locks, 2nd attempt