On Thu, Jul 11, 2013 at 5:11 PM, Michael Paquier <michael.paqu...@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
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
