Re: [PATCH] DefaultACLs - Mailing list pgsql-hackers

From Petr Jelinek
Subject Re: [PATCH] DefaultACLs
Date
Msg-id 4A986158.2040406@pjmodos.net
Whole thread Raw
In response to Re: [PATCH] DefaultACLs  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCH] DefaultACLs  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
I had some time to work on this patch, and I implemented the ALTER 
DEFAULT PRIVILEGES syntax as proposed by Tom and adjusted some other 
stuff, but before I can submit the new patch for commitfest there is 
still this fundamental issue about how it should behave.

The situation is as following. Josh's and Stephen's idea was basically 
to solve something like this: you are a dba, you give some users 
privileges to create tables and you want those new tables to have same 
privileges no matter who created them.
But if I understood Tom's suggestions correctly then his approach does 
not solve this at all since every one of those users with CREATE TABLE 
privileges would have to also set same DEFAULT PRIVILEGES and the dba 
would have no say in the matter.

I personally can see use cases for both but I don't really see any 
reasonable way to have both at the same time.

-- 
Regards
Petr Jelinek (PJMODOS)



pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: Linux LSB init script
Next
From: David Fetter
Date:
Subject: Re: Linux LSB init script