pg_basebackup copies the data directory permission mode from the
upstream server. But it doesn't copy the ownership. So if say the
upstream server allows group access and things are owned by
postgres:postgres, and I want to make a copy for local development and
make a backup into a directory owned by peter:staff without group
access, then it would be inappropriate for pg_basebackup to change the
permissions on that directory.
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?
comments?
Regards,
Haribabu Kommi
Fujitsu Australia
