Re: DROP INDEX CONCURRENTLY is not really concurrency safe & leaves around undroppable indexes - Mailing list pgsql-hackers

From Abhijit Menon-Sen
Subject Re: DROP INDEX CONCURRENTLY is not really concurrency safe & leaves around undroppable indexes
Date
Msg-id 20121018115651.GA1796@toroid.org
Whole thread Raw
In response to Re: DROP INDEX CONCURRENTLY is not really concurrency safe & leaves around undroppable indexes  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Re: DROP INDEX CONCURRENTLY is not really concurrency safe & leaves around undroppable indexes  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
At 2012-09-25 01:46:18 +0200, andres@2ndquadrant.com wrote:
>
> The attached patch fixes this issue. Haven't looked at the other one
> in detail yet.

Here are tests for both bugs. They currently fail with HEAD.

Note that the first test now uses PREPARE instead of the SELECTs in the
original example, which no longer works after commit #96cc18 because of
the re-added AcceptInvalidationMessages calls (archaeology by Andres).

-- Abhijit

Attachment

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Deprecations in authentication
Next
From: Simon Riggs
Date:
Subject: Re: Re: DROP INDEX CONCURRENTLY is not really concurrency safe & leaves around undroppable indexes