Skip site navigation (1) Skip section navigation (2)

Re: Should I implement DROP INDEX CONCURRENTLY?

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, 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-01-19 15:02:31
Message-ID: CA+U5nMLMKWEs84Zgc5Px-JTOT5Ea=Csvs0p8or39=WWsXmd08g@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Wed, Jan 18, 2012 at 11:12 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Wed, Jan 18, 2012 at 5:49 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> Can I just check with you that the only review comment is a one line
>> change? Seems better to make any additional review comments in one go.
>
> No, I haven't done a full review yet - I just noticed that right at
> the outset and wanted to be sure that got addressed.  I can look it
> over more carefully, and test it.

Corrected your point, and another found during retest.

Works as advertised, docs corrected.

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

Attachment: drop_index_concurrently.v2.patch
Description: text/x-patch (24.4 KB)

In response to

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2012-01-19 15:18:55
Subject: Re: Simulating Clog Contention
Previous:From: Peter GeogheganDate: 2012-01-19 14:49:50
Subject: Re: Simulating Clog Contention

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group