From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Maksim Milyutin <milyutinma(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Hint to set owner for tablespace directory |
Date: | 2018-09-11 15:10:49 |
Message-ID: | 8aa308d4-347a-52a3-0294-f0672b091a7e@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 07/09/2018 17:59, Maksim Milyutin wrote:
>> You are still proposing to hint that the permissions on the tablespace
>> directory might be correct but that the main database instance is
>> running under the wrong user.
> Not exactly this way. The case that motivated me to make this patch was
> the novice user after installing postgres from package (with setting up
> postgres user and initializing PGDATA with right permissions) tried to
> create the necessary tablespace directories from himself (the owner of
> those directories was that user). The error message "could not set
> permissions on directory ..." disoriented that user. The need to change
> the owner of those directories came after careful reading of
> documentation. I think it would be helpful to show the proposed hint to
> more operatively resolve the problem.
I think it might be worth clarifying the documentation instead. I'm
looking at the CREATE TABLESPACE reference page and it's not super clear
on first reading.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2018-09-11 15:11:29 | Re: StandbyAcquireAccessExclusiveLock doesn't necessarily |
Previous Message | Fabien COELHO | 2018-09-11 14:57:33 | Re: pgbench - add pseudo-random permutation function |