Message-ID: <480A3F49.7080406@commandprompt.com>
Date: Sat, 19 Apr 2008 11:51:53 -0700
From: "Joshua D. Drake" <jd@commandprompt.com>
Organization: Command Prompt, Inc.
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Graham Leggett <minfrin@sharp.fm>
CC: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-admin@postgresql.org
Subject: Re: Could not create a tablespace - permission denied
References: <4809EC7B.6060902@sharp.fm> <9189.1208619241@sss.pgh.pa.us>
	<480A12F5.5060609@sharp.fm> <9478.1208620229@sss.pgh.pa.us>
	<480A190B.80408@sharp.fm> <480A1A55.6090800@commandprompt.com>
	<480A381D.3030908@sharp.fm>
In-Reply-To: <480A381D.3030908@sharp.fm>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Graham Leggett wrote:
> Joshua D. Drake wrote:
> 
>> I am pretty sure you are missing something. I can not reproduce your 
>> issue:
> 
> Do it like this:
> 
> - mkdir /tmp/foo
> - chown user:user /tmp/foo
> - edit /etc/group and add postgres to the group user

Aha! there it is. Adding a user to a group doesn't mean anything until 
that user reinitializes the environment. That is why restarting 
postgresql resolves the issue. When postgresql is started, is actually 
launches a new shell as the user and the fact that they are part of the 
group is picked up.


Sincerely,

Joshua D. Drake