Re: Should I implement DROP INDEX CONCURRENTLY?

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Daniel Farina <daniel(at)heroku(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Should I implement DROP INDEX CONCURRENTLY?
Date: 2012-02-01 19:31:12
Message-ID: 1328124672.28270.3.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On sön, 2012-01-29 at 22:01 +0000, Simon Riggs wrote:
> Patch now locks index in AccessExclusiveLock in final stage of drop.

Doesn't that defeat the point of doing the CONCURRENTLY business in the
first place?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2012-02-01 19:39:00 Re: Should I implement DROP INDEX CONCURRENTLY?
Previous Message Simon Riggs 2012-02-01 19:25:08 Re: some longer, larger pgbench tests with various performance-related patches