Re: tablespaces and non-empty directories

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Zeugswetter Andreas DCP SD" <ZeugswetterA(at)spardat(dot)at>
Cc: "Philip Yarra" <philip(at)utiba(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: tablespaces and non-empty directories
Date: 2005-11-17 14:34:08
Message-ID: 25791.1132238048@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Zeugswetter Andreas DCP SD" <ZeugswetterA(at)spardat(dot)at> writes:
>> No. There is no reason to use a volume's root directory as a
>> tablespace;
>> especially so since the root directory ought to be owned by root

> That is not so on AIX. Only the moint point (the dir in the parent) is
> root.
> Once mounted it can have (and preserves) any permission you want.

Yeah, you *can* make it not-root-owned on most Unixen. That doesn't
mean it's a good idea to do so. For instance, if the root directory
is owned by Joe Luser, what's to stop him from blowing away lost+found
and thereby screwing up future fscks? You should basically never have
more-privileged objects (such as lost+found) inside directories owned by
less-privileged users --- it's just asking for trouble.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-11-17 14:41:10 Re: MERGE vs REPLACE
Previous Message Tom Lane 2005-11-17 14:26:14 Re: Numeric 508 datatype