Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g6xWG-0004eE-J5 for pgsql-hackers@arkaria.postgresql.org; Mon, 01 Oct 2018 12:41:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g6xWF-0001az-3v for pgsql-hackers@arkaria.postgresql.org; Mon, 01 Oct 2018 12:41:47 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g6xWE-0001as-Mf for pgsql-hackers@lists.postgresql.org; Mon, 01 Oct 2018 12:41:46 +0000 Received: from mail-ed1-x544.google.com ([2a00:1450:4864:20::544]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1g6xWB-00033W-4j for pgsql-hackers@postgresql.org; Mon, 01 Oct 2018 12:41:45 +0000 Received: by mail-ed1-x544.google.com with SMTP id f38-v6so14035386edd.8 for ; Mon, 01 Oct 2018 05:41:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=ye62s1mL9Zm2StEI9wbClumx2DQvSrQX5tE3LOayDQc=; b=VGYJu3E385fzfBlwN7YShL3WTbZgcPY+79av9phqClL4Z+KJXNHwGeu3TNuX3MPJzX AKOKIyYjVClWbqKPp4ZTWODY/8mTCF38Jtsi1d6DAteWSCK4AXGLB15A9mSGbu41znjl 9KKqqAo3os9M8GIfI4eH811szekKk1Pc9k9w3Fa3v/TasRSWuYJuhQd6Xmrjf9if3vjL 3waWzbwcVi6fhYeJnKdFSkHkRu3BxcorU5WmihH/G1ZC2dUd7sKEq4tMu/vMM6VhbsR2 oGlnUfn7Qb2asXNReYrG23Ra2mJWx0MYMSJ4EL3iQwCtCdYUvP7aPpIhg3PulOubaONu 4LMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=ye62s1mL9Zm2StEI9wbClumx2DQvSrQX5tE3LOayDQc=; b=ATst8q2qiWlX+HJuvv4xM+VERiCa+B4i82Dn0C/D+l4fWu2Z0THj3xkL/T+Hhfk7x0 CKh+Z4L+7CuFcGYQzN1W89cH7zW2LTZVqHHkYfVTF+lvrLiUiLS/Cjx/1CY3l9GOGoSz 5VP0Zs/rI8zFHqHKmOxCdOoiKkw5K13jYkOAc9+IiFJyV89XCz0Wb1AnH/llIWsUUEHF XRB8Ipud0utlNga+zwZQ5aAWaTzrOLp4glJtFtqsCKXzkad5cSaDIeDmyKJ11L4IyyEM 9zN+RQi5d05HZFGBEeK9+gP6Ih2+maXtQfvozD7UfkBFsaKgw6MiY2u6wDs9gFz5qQmL BOKQ== X-Gm-Message-State: ABuFfoijhZccSalGNKnjGJynL1llKqFRrg3pqWCgo3eChIeTIserY12O AekxBB1sZE2oVvPerNWK77a9pnr/ZxU= X-Google-Smtp-Source: ACcGV61BWlzGz/d1cRg1Oau3ahNNV9DvPC+ppksQ2btlI6/0MyLiXkyAIUKMEQmOhxGX88ahSsBuzg== X-Received: by 2002:a17:906:c7d3:: with SMTP id dc19-v6mr1470232ejb.232.1538397700951; Mon, 01 Oct 2018 05:41:40 -0700 (PDT) Received: from MacBook-Pro-Milutin.local ([193.30.236.200]) by smtp.gmail.com with ESMTPSA id l12-v6sm4245098edn.77.2018.10.01.05.41.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 01 Oct 2018 05:41:40 -0700 (PDT) Subject: Re: Hint to set owner for tablespace directory To: Peter Eisentraut Cc: Tom Lane , PostgreSQL-development References: <5ca60e1a-26f9-89fd-e912-021dd2b8afe2@gmail.com> <1bc2bc14-e42a-8d9c-d47c-3afac05de347@2ndquadrant.com> <2615ea98-6537-1fcf-667a-09022063336a@postgrespro.ru> <17440.1535723980@sss.pgh.pa.us> <91828914-cfa2-b186-01e3-68a39a77f497@gmail.com> <8aa308d4-347a-52a3-0294-f0672b091a7e@2ndquadrant.com> <542444d9-d768-aa10-07c1-83abd896e86f@2ndquadrant.com> From: Maksim Milyutin Message-ID: Date: Mon, 1 Oct 2018 15:41:38 +0300 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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