Re: tablespaces and non-empty directories

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


> > This is because lost+found exists. Since lost+found would be a
> > reasonably common directory to find at a mount-point on Unix-like
> > OSs*, would it make sense for CREATE TABLESPACE to ignore it if
present?

> 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.
But on AIX the workaround is to remove the directory after mounting and
before
creating the tablespace.

Andreas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas DCP SD 2005-11-17 11:34:30 Re: MERGE vs REPLACE
Previous Message Csaba Nagy 2005-11-17 09:59:39 Re: MERGE vs REPLACE