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

From Michael Paquier
Subject Re: Support for REINDEX CONCURRENTLY
Date
Msg-id CAB7nPqTGa_my7yUYxJqeH_0eYPLRyrGiHXhKOKNLkmVLLWu6uQ@mail.gmail.com
Whole thread Raw
In response to Re: Support for REINDEX CONCURRENTLY  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Support for REINDEX CONCURRENTLY
List pgsql-hackers
On Thu, Jul 11, 2013 at 5:11 PM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> I am resending the patches after Fujii-san noticed a bug allowing to
> even drop valid toast indexes with the latest code... While looking at
> that, I found a couple of other bugs:
> - two bugs, now fixed, with the code path added in tablecmds.c to
> allow the manual drop of invalid toast indexes:
> -- Even a user having no permission on the parent toast table could
> drop an invalid toast index
> -- A lock on the parent toast relation was not taken as it is the case
> for all the indexes dropped with DROP INDEX
> - Trying to reindex concurrently a mapped catalog leads to an error.
> As they have no relfilenode, I think it makes sense to block reindex
> concurrently in this case, so I modified the core patch in this sense.
This patch status has been changed to returned with feedback.
--
Michael



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: mvcc catalo gsnapshots and TopTransactionContext
Next
From: Josh Berkus
Date:
Subject: Re: [PERFORM] In progress INSERT wrecks plans on table