On Sun, Jan 17, 2016 at 01:57:22PM -0500, Stephen Frost wrote: > Right, we also check in the backend on startup for certain permissions. > I don't recall offhand if that's forced to 700 or if we allow 750. > > > > I don't recall offhand if that means we'd have to make changes to allow > > > that, but, for my 2c, I don't see why we wouldn't allow it to be an > > > option. > > > > OK, that would be an initdb change then. > > It would need to be optional, so distributions and users could choose > which makes sense for their systems.
While the group owner of the directory is a distributions question, the permissions are usually a backup-method-specific requirement. I can see us creating an SQL function that opens up group permissions on the data directory for specific backup tools that need it, then granting permissions on that function to the backup role. This is another example where different backup tools need different permissions. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Roman grave inscription + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
