30.08.2018 19:52, Peter Eisentraut wrote:
> On 23/08/2018 13:24, Maksim Milyutin wrote:
>> I have noticed the novice users are stuck trying to create tablespace
>> over a directory whose owner is not the system postgres user. They
>> observed the message "could not set permissions on directory ...:
>> permission denied".
>>
>> I want to add patch that prints hint to set required owner for the
>> tablespace directory if this is the cause of the problem (*errno ==
>> EPERM* after calling *chmod*).
> I think the hint is backwards. When you don't have permission to chmod
> the tablespace directory, you probably want to fix the permissions on
> the tablespace directory or its parent.
According with man page of chmod(2) when permissions on parent
directories are insufficient the errno takes the EACCES value. However,
in Linux man page of chmod(2) there been mentioned that the process
could be not privileged (does not have the CAP_FOWNER capability) when
errno is EPERM.
> But the hint says to run the database server as a different user. That's a bit unusual.
In this case I propose to:
- replace my initial hint message to the guess what to do if errno ==
EPERM, smth like "You might need to install the PostgreSQL system user
as the owner of this directory";
- add another hint if errno == EACCES: "Fix permissions on the parent
directories".
Any thoughts?
--
Regards,
Maksim Milyutin