Re: Column-Level Privileges - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: Column-Level Privileges
Date
Msg-id 20090122204510.GG32428@tamriel.snowman.net
Whole thread Raw
In response to Re: Column-Level Privileges  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Column-Level Privileges  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
* Tom Lane (tgl@sss.pgh.pa.us) wrote:
> Applied with revisions.  The main externally visible change is that I
> implemented per-column REFERENCES privilege, since that's required by
> spec.  I did some heavy revision of the parsing support too, as per
> previous dicussions, and editorial cleanup and bugfixing elsewhere.

Great!  Glad to hear it, and thanks for the updates and handling
REFERENCES.

> There are still some significant loose ends though:
[...]

I'll work on these and plan to finish them by Monday.

> * Perhaps it would be appropriate to let LOCK TABLE succeed if you have
> proper permissions on at least one column of the table.  However, it's
> bad enough that LOCK TABLE examines permissions before locking the table
> now; I don't think it ought to be grovelling through the columns without
> lock.  So this might be a place to leave well enough alone.

Agreed.
Thanks,
    Stephen

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Pluggable Indexes (was Re: rmgr hooks (v2))
Next
From: Alvaro Herrera
Date:
Subject: autovacuum, reloptions, and hardcoded pg_class tupdesc