| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | David Steele <david(at)pgmasters(dot)net>, 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 12:38:44 |
| Message-ID: | 7669.1488803924@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> 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
I'd ask what is the point, considering that we don't view "cp -a" as a
supported backup technique in the first place.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Berg | 2017-03-06 12:42:33 | Re: One-shot expanded output in psql using \gx |
| Previous Message | Masahiko Sawada | 2017-03-06 12:37:58 | Re: pgsql: Allow vacuums to report oldestxmin |