Re: [HACKERS] PATCH: Configurable file mode mask - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: [HACKERS] PATCH: Configurable file mode mask
Date
Msg-id CANP8+jKFXxUd9TA2iTJWYnsZaGEQEcWoZceYHsc1bnGD76Pd8A@mail.gmail.com
Whole thread Raw
In response to [HACKERS] PATCH: Configurable file mode mask  (David Steele <david@pgmasters.net>)
Responses Re: [HACKERS] PATCH: Configurable file mode mask  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [HACKERS] PATCH: Configurable file mode mask  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On 1 March 2017 at 01:58, David Steele <david@pgmasters.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



pgsql-hackers by date:

Previous
From: Michael Banck
Date:
Subject: Re: [HACKERS] Parallel Index Scans
Next
From: Amit Kapila
Date:
Subject: Re: [HACKERS] Parallel Index Scans