Re: BUG #5609: Exclusive Locks & Permission

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Rob Brucks <rob(dot)brucks(at)rackspace(dot)com>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #5609: Exclusive Locks & Permission
Date: 2010-08-09 20:21:01
Message-ID: 13390.1281385261@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Rob Brucks <rob(dot)brucks(at)rackspace(dot)com> writes:
> 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)?

Not directly. You might be able to do something with hiding the tables
in schemas that the unprivileged user hasn't got USAGE rights on, so
that he can't even name them. But I suspect that having to qualify
table names with schema names is more code change than you want.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2010-08-10 02:05:32 Re: BUG #5603: pg_tblspc and pg_twoface directories get deleted when starting up service
Previous Message Rob Brucks 2010-08-09 19:47:02 Re: BUG #5609: Exclusive Locks & Permission