Bruce Momjian <[EMAIL PROTECTED]> writes: > Here is how I think SQL-level row permissions would work:
> We already have an optional OID system column that can be specified > during table creation (WITH OIDS). We could have another optional oid > column (WITH ROW SECURITY) called security_context which would store the > oid of the role that can see the row; if the oid is zero (InvalidOid), > anyone can see it. SE-PostgreSQL would default to WITH ROW SECURITY and > use the oid to look up strings in pg_security. This is just a different syntax for KaiGai's label storage implementation. It doesn't really answer any of the hard questions, like what the heck is the behavior of foreign keys. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers