From: | Maksim Milyutin <milyutinma(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(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-07 15:59:34 |
Message-ID: | 91828914-cfa2-b186-01e3-68a39a77f497@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 09/07/2018 06:05 PM, Peter Eisentraut wrote:
> On 07/09/2018 11:59, Maksim Milyutin wrote:
>> OK. However I think it would be helpful to leave the mention about
>> setting necessary owner for tablespace directory. My final version of
>> hint is "You might need to fix permissions on this directory or its
>> parents or install the PostgreSQL system user as the owner of this
>> directory." And updated version of patch is attached.
> 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.
--
Regards, Maksim Milyutin
From | Date | Subject | |
---|---|---|---|
Next Message | James Coleman | 2018-09-07 16:17:25 | Partial index plan/cardinality costing |
Previous Message | Chris Travers | 2018-09-07 15:57:05 | [PATCH] Fix for infinite signal loop in parallel scan |