Re: Should I implement DROP INDEX CONCURRENTLY?
Simon Riggs <simon@2ndquadrant.com>
From: Simon Riggs <simon@2ndQuadrant.com>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Daniel Farina <daniel@heroku.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2011-12-31T13:26:25Z
Lists: pgsql-hackers
Attachments
- drop_index_concurrently.v1.patch (text/x-patch) patch v1
On Fri, Dec 30, 2011 at 10:20 PM, Peter Eisentraut <peter_e@gmx.net> wrote: > On ons, 2011-08-24 at 11:24 -0700, Daniel Farina wrote: >> I was poking around at tablecmds and index.c and wonder if a similar >> two-pass approach as used by CREATE INDEX CONCURRENTLY can be used to >> create a DROP INDEX CONCURRENTLY, and if there would be any interest >> in accepting such a patch. > > Hmm, it seems I just independently came up with this same concept. My > problem is that if a CREATE INDEX CONCURRENTLY fails, you need an > exclusive lock on the table just to clean that up. If the table is > under constant load, you can't easily do that. So a two-pass DROP INDEX > CONCURRENTLY might have been helpful for me. Here's a patch for this. Please review. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services