Postgres Pro
Downloads
Home   >   mailing lists

Re: Should I implement DROP INDEX CONCURRENTLY? - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Should I implement DROP INDEX CONCURRENTLY?
Date
Msg-id CA+U5nMLDq_xCVPL5FR5=-0yU5yzzNs8+0RaZ_R2wnUrzxYb2ow@mail.gmail.com
Whole thread Raw
In response to Re: Should I implement DROP INDEX CONCURRENTLY?  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: Should I implement DROP INDEX CONCURRENTLY?  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-hackers
Tree view 
On Wed, Jan 4, 2012 at 11:14 AM, Simon Riggs <simon@2ndquadrant.com> wrote:

> Not having a freelist at all is probably a simpler way of avoiding the
> lock contention, so I'll happily back that suggestion instead. Patch
> attached, previous patch revoked.

v2 attached with cleanup of some random stuff that crept onto patch.

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

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Intermittent regression test failures from index-only plan changes
Next
From: Simon Riggs
Date:
Subject: Re: bgwriter holds onto file handles of deleted files