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

From Simon Riggs
Subject Re: Re: DROP INDEX CONCURRENTLY is not really concurrency safe & leaves around undroppable indexes
Date
Msg-id CA+U5nMKK99t3o_Fbs4UH+PQK9rBWu=ctam60zUZ0kbKAtcs+vA@mail.gmail.com
Whole thread Raw
In response to Re: DROP INDEX CONCURRENTLY is not really concurrency safe & leaves around undroppable indexes  (Abhijit Menon-Sen <ams@2ndQuadrant.com>)
List pgsql-hackers
On 18 October 2012 12:56, Abhijit Menon-Sen <ams@2ndquadrant.com> wrote:
> 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).

Thanks, I'll apply these now.

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



pgsql-hackers by date:

Previous
From: Abhijit Menon-Sen
Date:
Subject: Re: DROP INDEX CONCURRENTLY is not really concurrency safe & leaves around undroppable indexes
Next
From: "Kevin Grittner"
Date:
Subject: Re: Bugs in CREATE/DROP INDEX CONCURRENTLY