| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Adam Brightwell <adam(dot)brightwell(at)crunchydata(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Subject: | Re: PATCH: Configurable file mode mask |
| Date: | 2017-03-06 11:27:15 |
| Message-ID: | CANP8+jKFXxUd9TA2iTJWYnsZaGEQEcWoZceYHsc1bnGD76Pd8A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1 March 2017 at 01:58, David Steele <david(at)pgmasters(dot)net> wrote:
> PostgreSQL currently requires the file mode mask (umask) to be 0077.
> However, this precludes the possibility of a user in the postgres group
> performing a backup (or whatever). Now that
> pg_start_backup()/pg_stop_backup() privileges can be delegated to an
> unprivileged user, it makes sense to also allow a (relatively)
> unprivileged user to perform the backup at the file system level as well.
+1
> This patch introduces a new initdb param, -u/-file-mode-mask, and a new
> GUC, file_mode_mask,
Why both initdb and at server start? Seems like initdb is OK, or in pg_control.
> to allow the default mode of files and directories
> in the $PGDATA directory to be modified.
Are you saying if this is changed all files/directories will be
changed to the new mode?
It seems like it would be annoying to have some files in one mode,
some in another.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2017-03-06 11:33:50 | Re: Parallel Index Scans |
| Previous Message | Michael Banck | 2017-03-06 11:27:10 | Re: Parallel Index Scans |