| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_basebackup ignores the existing data directory permissions |
| Date: | 2019-03-18 12:36:14 |
| Message-ID: | 311ebaca-ed53-51bc-7ef9-6f3f7e4da481@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-03-16 15:29, Robert Haas wrote:
> Another option would be to provide a pg_basebackup option to allow the
> user to specify what they intended i.e. --[no-]group-read. (Tying it
> to -R doesn't sound like a good decision to me.)
I was actually surprised to learn how it works right now. I would have
preferred that pg_basebackup require an explicit option to turn on group
access, similar to initdb.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2019-03-18 12:38:22 | Re: pg_basebackup ignores the existing data directory permissions |
| Previous Message | Peter Eisentraut | 2019-03-18 12:33:12 | Re: Add exclusive backup deprecation notes to documentation |