Re: [RFC] PostgreSQL Access Control Extension (PGACE) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [RFC] PostgreSQL Access Control Extension (PGACE)
Date
Msg-id 12044.1176766164@sss.pgh.pa.us
Whole thread Raw
In response to Re: [RFC] PostgreSQL Access Control Extension (PGACE)  ("Andrew Dunstan" <andrew@dunslane.net>)
Responses Re: [RFC] PostgreSQL Access Control Extension (PGACE)  (Andrew Dunstan <andrew@dunslane.net>)
Re: [RFC] PostgreSQL Access Control Extension (PGACE)  (KaiGai Kohei <kaigai@kaigai.gr.jp>)
Re: [RFC] PostgreSQL Access Control Extension (PGACE)  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
"Andrew Dunstan" <andrew@dunslane.net> writes:
> What's more, we have a SoC project for column level access controls.

... which presumably wouldn't involve any added dependency on outside code.
For people who are already using SELinux or Trusted Solaris, making the
database dependent on that infrastructure might be seen as a plus, but
I'm not sure the rest of the world would be pleased.  There are also
some interesting questions about SQL spec compliance and whether a
database that silently hides some rows from you will give semantically
consistent results.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [RFC] PostgreSQL Access Control Extension (PGACE)
Next
From: "Florian G. Pflug"
Date:
Subject: Re: RESET command seems pretty disjointed now