From: Tom Lane <tgl@sss.pgh.pa.us>
To: Graham Leggett <minfrin@sharp.fm>
Cc: pgsql-admin@postgresql.org
Subject: Re: Could not create a tablespace - permission denied
Date: Sat, 19 Apr 2008 11:50:29 -0400
Message-ID: <9478.1208620229@sss.pgh.pa.us> (raw)
In-Reply-To: <480A12F5.5060609@sharp.fm>
References: <4809EC7B.6060902@sharp.fm>
<9189.1208619241@sss.pgh.pa.us>
<480A12F5.5060609@sharp.fm>
Graham Leggett <minfrin@sharp.fm> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, minfrin@sharp.fm
Subject: Re: Could not create a tablespace - permission denied
In-Reply-To: <9478.1208620229@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox