Sorry about that, I hit the submit button on accident before I finished typing out the issue. But I guess there was enough there for you to understand the problem.
Thanks for the quick response. Is there any alternative I can use to prevent the exclusive lock (other than changing the app, we don't have access to the source code)? Thanks, Rob -----Original Message----- From: Tom Lane [mailto:t...@sss.pgh.pa.us] Sent: Monday, August 09, 2010 2:41 PM To: Rob Brucks Cc: pgsql-bugs@postgresql.org Subject: Re: [BUGS] BUG #5609: Exclusive Locks & Permission "Rob Brucks" <rob.bru...@rackspace.com> writes: > The user's permissions need to be checked before requesting an exclusive > lock on the table for the alter. Unfortunately, that cure is as bad or worse than the disease. It's not possible to do a permissions check before acquiring any lock --- what if somebody is changing the permissions under you, or even dropping or renaming the table? We could acquire sharelock, do the permissions check, and then upgrade to exclusive lock; but lock upgrading has its own unpleasant consequences, notably increased risk of deadlock. So it's unlikely this is going to get changed. regards, tom lane Confidentiality Notice: This e-mail message (including any attached or embedded documents) is intended for the exclusive and confidential use of the individual or entity to which this message is addressed, and unless otherwise expressly indicated, is confidential and privileged information of Rackspace. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at ab...@rackspace.com, and delete the original message. Your cooperation is appreciated. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
