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

From Robert Haas
Subject Re: Should I implement DROP INDEX CONCURRENTLY?
Date
Msg-id CA+Tgmoa5u8M4UAdBJCnUArEz74osJ2T2WDBdFpMZ1Rp3nuTQyQ@mail.gmail.com
Whole thread Raw
In response to Re: Should I implement DROP INDEX CONCURRENTLY?  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Should I implement DROP INDEX CONCURRENTLY?
List pgsql-hackers
On Mon, Jan 16, 2012 at 2:06 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
> 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.

Maybe we should set both to false?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Why is CF 2011-11 still listed as "In Progress"?
Next
From: Alvaro Herrera
Date:
Subject: Re: foreign key locks, 2nd attempt