From: | Maksim Milyutin <milyutinma(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Hint to set owner for tablespace directory |
Date: | 2018-10-01 12:41:38 |
Message-ID: | d73e39a0-a25f-447f-4886-05b1bf915663@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
01.10.2018 15:15, Peter Eisentraut wrote:
> On 24/09/2018 14:50, Peter Eisentraut wrote:
>> On 11/09/2018 17:10, Peter Eisentraut wrote:
>>> On 07/09/2018 17:59, Maksim Milyutin wrote:
>>>> 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.
>> How about the attached patch?
> I have committed this patch and will close this commitfest item. I
> don't think the idea with the hints in the code was going anywhere.
>
Yes, thanks. Sorry for so delayed answer, I was busy. You have clearly
described the workflow to create tablespace (including *chown* command)
and in general it is enough to resolve the issue with wrong owner of
tablespace directory.
--
Regards,
Maksim Milyutin
From | Date | Subject | |
---|---|---|---|
Next Message | Etsuro Fujita | 2018-10-01 12:54:26 | Re: de-deduplicate code in DML execution hooks in postgres_fdw |
Previous Message | Daniel Gustafsson | 2018-10-01 12:37:42 | Re: [HACKERS] Optional message to user when terminating/cancelling backend |