Re: Support for REINDEX CONCURRENTLY - Mailing list pgsql-hackers

From Jeremy Harris
Subject Re: Support for REINDEX CONCURRENTLY
Date
Msg-id 50703D45.9070307@wizmail.org
Whole thread Raw
In response to Re: Support for REINDEX CONCURRENTLY  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 10/05/2012 09:03 PM, Tom Lane wrote:
> Note that allowing subsequent requests to jump the queue would not be a
> good fix for this; if you do that, it's likely the ex-lock will never be
> granted, at least not till the next system idle time.

Offering that option to the admin sounds like a good thing, since
(as Alvaro points out) the build of the replacement index could take
considerable time but be done without the lock.  Then the swap
done in the first quiet period (but without further admin action),
and the drop started.

One size doesn't fit all.  It doesn't need to be the only method.
-- 
Cheers,    Jeremy




pgsql-hackers by date:

Previous
From: Amit kapila
Date:
Subject: Re: Re: [WIP] Performance Improvement by reducing WAL for Update Operation
Next
From: Tom Lane
Date:
Subject: Re: Add FET to Default and Europe.txt