column-level update privs + lock table - Mailing list pgsql-general

From Josh Kupershmidt
Subject column-level update privs + lock table
Date
Msg-id AANLkTimVe-V4rbnJa-QTAnz-703vCUEH9tMd9g6VbXAj@mail.gmail.com
Whole thread Raw
Responses Re: column-level update privs + lock table  (Josh Kupershmidt <schmiddy@gmail.com>)
List pgsql-general
Hi all,

I noticed that granting a user column-level update privileges doesn't
allow that user to issue LOCK TABLE with any mode other than Access
Share.

The documentation page for LOCK TABLE claims: "All other forms of LOCK
require at least one of UPDATE, DELETE, or TRUNCATE privileges.", and
I don't see a good reason why column-level privileges shouldn't be
enough to let the user use LOCK TABLE. Is this just an oversight?

Example below:

  CREATE ROLE unpriv WITH LOGIN;
  CREATE TABLE bar (id int primary key, comment text);
  GRANT SELECT ON bar TO unpriv;
  GRANT SELECT, UPDATE (comment) ON TABLE bar TO unpriv;

and then, as user "unpriv":

  BEGIN;
  LOCK TABLE bar IN ROW SHARE MODE;
  COMMIT;

Josh

pgsql-general by date:

Previous
From: Raymond O'Donnell
Date:
Subject: Re: [Slony1-general] [ANNOUNCE] Slony-I 2.0.5 Released
Next
From: Craig Ringer
Date:
Subject: Re: postgreSQL for Windows 7