| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Stephen Frost <sfrost(at)snowman(dot)net>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_basebackup ignores the existing data directory permissions |
| Date: | 2019-03-21 18:56:24 |
| Message-ID: | CA+Tgmoas4qmhPzr1LK8KWzmpbprmQjmd+Dz99jcX5oAU0CWc1w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 19, 2019 at 2:29 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> Hm. We have been assuming that the contents of a base backup inherit
> the permission of the source when using pg_basebackup because this
> allows users to keep a nodes in a consistent state without deciding
> which option to use. Do you mean that you would like to enforce the
> permissions of only the root directory if it exists? Or the root
> directory with all its contents? The former may be fine. The latter
> is definitely not.
Why not?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeremy Finzel | 2019-03-21 19:06:49 | Re: Automated way to find actual COMMIT LSN of subxact LSN |
| Previous Message | Daniel Gustafsson | 2019-03-21 18:54:30 | Re: [proposal] Add an option for returning SQLSTATE in psql error message |