| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> |
| Cc: | 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-14 23:33:44 |
| Message-ID: | 1a6d580f-edc6-1453-c6e2-9a493c95fdc0@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-03-09 02:19, Haribabu Kommi wrote:
> Yes, I agree that it may be a problem if the existing data directory
> permissions
> are 0700 to changing it to 0750. But it may not be a problem for the
> scenarios,
> where the existing data permissions >=0750, to the upstream permissions.
> Because user must need to change anyway to start the server, otherwise
> server
> start fails, and also the files inside the data folder follows the
> permissions of the
> upstream data directory.
>
> usually production systems follows same permissions are of upstream, I don't
> see a problem in following the same for development environment also?
I think the potential problems of getting this wrong are bigger than the
issue we are trying to fix.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2019-03-14 23:40:05 | Re: propagating replica identity to partitions |
| Previous Message | Mitar | 2019-03-14 23:19:40 | Re: Feature: temporary materialized views |