| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, 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:38:22 |
| Message-ID: | e7d5fe46-5a3f-c3da-7f33-566e14edd822@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-03-18 08:32, Magnus Hagander wrote:
> Going based on the current setting of the directory seems defensible to
> me, with the argument of "we trust you created the directory the way you
> want the rest of the system to be".
>
>
> Which I believe is also how a plain unix cp (or tar or whatever) would
> work, isn't it? I think that alone is a pretty strong reason to work the
> same as those -- they're not entirely unsimilar.
Those don't copy over the network. In the case of pg_basebackup, there
is nothing that ensures that the remote system has the same users or
groups or permission setup.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hugh Ranalli | 2019-03-18 13:06:09 | Re: Unaccent extension python script Issue in Windows |
| Previous Message | Peter Eisentraut | 2019-03-18 12:36:14 | Re: pg_basebackup ignores the existing data directory permissions |