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

From Simon Riggs
Subject Re: Should I implement DROP INDEX CONCURRENTLY?
Date
Msg-id CA+U5nM+c0ZZ9PB+fNh+MJT+4+_QUJb9xMk_woZ2OzbzjBM0s1A@mail.gmail.com
Whole thread Raw
In response to Re: Should I implement DROP INDEX CONCURRENTLY?  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Wed, Feb 1, 2012 at 2:56 AM, Robert Haas <robertmhaas@gmail.com> wrote:

> I improved the grammar issues in the attached version of the patch -
> the syntax is now simpler and more consistent, IF EXISTS now works,
> and RESTRICT is accepted (without changing the behavior) while CASCADE
> fails with a nicer error message.  I also fixed a bug in
> RangeVarCallbackForDropRelation.

Plus tests as well. Many thanks.

I fixed the main bug you observed and your test case now works
perfectly. I used pgbench to continuously drop/create an index, so a
little more than manual testing.

v5 Attached.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: JSON for PG 9.2
Next
From: Tom Lane
Date:
Subject: Re: Confusing EXPLAIN output in case of inherited tables