| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | kommi(dot)haribabu(at)gmail(dot)com, magnus(at)hagander(dot)net, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_basebackup ignores the existing data directory permissions |
| Date: | 2019-02-18 04:05:05 |
| Message-ID: | 20190218040505.GJ15532@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Feb 15, 2019 at 09:24:15AM +0900, Kyotaro HORIGUCHI wrote:
> I disagree that pg_basebackup rejects directories other than
> specific permissions, since it is just a binary backup tool,
> which is not exclusive to making replication-standby. It ought to
> be runnable and actually runnable by any OS users even by root,
> for who postgres rejects to start. As mentioned upthread, it is
> safe-side failure that server rejects to run on it.
Perhaps I do not fully understand your argument here. We do not
discuss about making pg_basebackup fail in any way, just of having it
adjust the umask of the target path so as users can simplify startups
using the generated base backup.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-02-18 04:07:43 | Re: make installcheck-world in a clean environment |
| Previous Message | Michael Paquier | 2019-02-18 04:01:20 | Re: Incorrect visibility test function assigned to snapshot |