Bruce Momjian <br...@momjian.us> writes:
> Alvaro Herrera wrote:
>> I thought it was impossible to use bare mountpoints as tablespaces due
>> to ownership problems ... Is that not the case? -1 for special hacks
>> that work around bogus setups, if that means intrusive changes to the
>> core code.
> I talked to the person who reported the problem and he and I confirmed
> that it is quite easy to make the mount point be owned by the postgres
> user and have that function as a tablespace. Is that not a supported
> setup?
It might be *possible*, but that doesn't make it a good idea. The
traditional sysadmin advice in this area is that mount points should
be owned by root. I don't really remember the reasoning but I'm pretty
sure I remember the principle.
> It was actually Tom's idea months ago to put a version-specific
> directory in the tablespace.
I was just about to re-suggest that. Why do you think it's such a
bad idea?
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
