Re: [HACKERS] grant with hierarchy option

2009-11-11 Thread Tom Lane
Peter Eisentraut writes: > On fre, 2009-10-30 at 00:49 -0400, Tom Lane wrote: >> And this is a problem why exactly? It's entirely likely that >> employee-ness can be determined just from what is visible in >> the persons view, anyway. Not to mention tableoid. > Yeah, tableoid is a deal-breaker.

Re: [HACKERS] grant with hierarchy option

2009-11-11 Thread Peter Eisentraut
On fre, 2009-10-30 at 00:49 -0400, Tom Lane wrote: > Peter Eisentraut writes: > > There is a gap in the permission scheme for inheritance setups. Say you > > have this: > > > CREATE TABLE persons (...); > > CREATE TABLE employees (...) INHERITS (persons); > > > GRANT SELECT ON persons TO foo; >

Re: [HACKERS] grant with hierarchy option

2009-10-29 Thread Tom Lane
Peter Eisentraut writes: > There is a gap in the permission scheme for inheritance setups. Say you > have this: > CREATE TABLE persons (...); > CREATE TABLE employees (...) INHERITS (persons); > GRANT SELECT ON persons TO foo; > Then user foo can extract who the employees are using > SELECT *

[HACKERS] grant with hierarchy option

2009-10-29 Thread Peter Eisentraut
There is a gap in the permission scheme for inheritance setups. Say you have this: CREATE TABLE persons (...); CREATE TABLE employees (...) INHERITS (persons); GRANT SELECT ON persons TO foo; Then user foo can extract who the employees are using SELECT * FROM persons EXCEPT SELECT * FROM ONLY