| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Andres Freund <andres(at)2ndquadrant(dot)com> |
| Subject: | Re: Re: DROP INDEX CONCURRENTLY is not really concurrency safe & leaves around undroppable indexes |
| Date: | 2012-10-18 12:19:26 |
| Message-ID: | CA+U5nMKK99t3o_Fbs4UH+PQK9rBWu=ctam60zUZ0kbKAtcs+vA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 18 October 2012 12:56, Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com> wrote:
> 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).
Thanks, I'll apply these now.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2012-10-18 12:58:43 | Re: Bugs in CREATE/DROP INDEX CONCURRENTLY |
| Previous Message | Abhijit Menon-Sen | 2012-10-18 11:56:51 | Re: DROP INDEX CONCURRENTLY is not really concurrency safe & leaves around undroppable indexes |