Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 59D082E0032 for ; Sat, 19 Apr 2008 12:50:33 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 73076-05 for ; Sat, 19 Apr 2008 12:50:31 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by developer.postgresql.org (Postfix) with ESMTP id 26A912E0033 for ; Sat, 19 Apr 2008 12:50:31 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m3JFoTbH009479; Sat, 19 Apr 2008 11:50:30 -0400 (EDT) To: Graham Leggett cc: pgsql-admin@postgresql.org Subject: Re: Could not create a tablespace - permission denied In-reply-to: <480A12F5.5060609@sharp.fm> References: <4809EC7B.6060902@sharp.fm> <9189.1208619241@sss.pgh.pa.us> <480A12F5.5060609@sharp.fm> Comments: In-reply-to Graham Leggett message dated "Sat, 19 Apr 2008 17:42:45 +0200" Date: Sat, 19 Apr 2008 11:50:29 -0400 Message-ID: <9478.1208620229@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/200 X-Sequence-Number: 28964 Graham Leggett writes: > At it turned out, the postgresql server had cached the system user > permissions, and it only started working after postgresql had been > restarted and the cached credentials had been replaced. I think this explanation is fiction ... there is no "cacheing of credentials" in there that I know about. Maybe the server had not been running under the userid you thought it was? But it would have to match the ownership of the data directory, so it's hard to see how a simple restart would fix it. [ thinks... ] Hm, is the tablespace directory mounted over NFS? I *have* heard of strange cacheing behaviors on NFS. In fact, NFS has enough weirdnesses that I wouldn't recommend running a database over it ... regards, tom lane