From: Tom Lane <tgl@sss.pgh.pa.us>
To: Maksim Milyutin <milyutinma@gmail.com>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Hint to set owner for tablespace directory
Date: Fri, 31 Aug 2018 09:59:40 -0400
Message-ID: <17440.1535723980@sss.pgh.pa.us> (raw)
In-Reply-To: <2615ea98-6537-1fcf-667a-09022063336a@postgrespro.ru>
References: <5ca60e1a-26f9-89fd-e912-021dd2b8afe2@gmail.com>
<1bc2bc14-e42a-8d9c-d47c-3afac05de347@2ndquadrant.com>
<2615ea98-6537-1fcf-667a-09022063336a@postgrespro.ru>
Maksim Milyutin <milyutinma@gmail.com> writes:
> 30.08.2018 19:52, Peter Eisentraut wrote:
>> 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.
> 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".
I agree with what I think Peter is saying: the hint should just recommend
fixing permissions on the directory, for either errno code. The more
detail you try to give, the more likely the hint will be wrong
... especially when you're dealing with errno codes that aren't all that
well standardized, as these aren't.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, milyutinma@gmail.com, peter.eisentraut@2ndquadrant.com
Subject: Re: Hint to set owner for tablespace directory
In-Reply-To: <17440.1535723980@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox