Re: DROP INDEX CONCURRENTLY is not really concurrency safe & leaves around undroppable indexes

From: Abhijit Menon-Sen <ams(at)2ndQuadrant(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>
Subject: Re: DROP INDEX CONCURRENTLY is not really concurrency safe & leaves around undroppable indexes
Date: 2012-10-18 11:56:51
Message-ID: 20121018115651.GA1796@toroid.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At 2012-09-25 01:46:18 +0200, andres(at)2ndquadrant(dot)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 Content-Type Size
dic-tests.diff text/x-diff 5.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2012-10-18 12:19:26 Re: Re: DROP INDEX CONCURRENTLY is not really concurrency safe & leaves around undroppable indexes
Previous Message Simon Riggs 2012-10-18 11:43:34 Re: Deprecations in authentication