Re: [HACKERS] tablespaces and non-empty directories

2005-11-22 Thread Tom Lane
Alvaro Herrera <[EMAIL PROTECTED]> writes: > Jim C. Nasby wrote: >> Along those lines, is there anything else that would benefit from being >> moved? pg_clog and pg_subtrans come to mind; but maybe pg_multixact and >> pg_twophase are candidates as well? > Hmm, I doubt moving any of the SLRU files

Re: [HACKERS] tablespaces and non-empty directories

2005-11-22 Thread Philip Yarra
On Wed, 23 Nov 2005 11:23 am, Gavin Sherry wrote: > > Along those lines, is there anything else that would benefit from being > > moved? pg_clog and pg_subtrans come to mind; but maybe pg_multixact and > > pg_twophase are candidates as well? > > pgsql_tmp Does anyone have any recommendations about

Re: [HACKERS] tablespaces and non-empty directories

2005-11-22 Thread Alvaro Herrera
Jim C. Nasby wrote: > On Tue, Nov 22, 2005 at 01:38:34PM -0500, Bruce Momjian wrote: > > > > * Allow the pg_xlog directory location to be specified during initdb > > with a symlink back to the /data location > > > > I think the only reason it is not done yet is because it is so easy to

Re: [HACKERS] tablespaces and non-empty directories

2005-11-22 Thread Gavin Sherry
On Tue, 22 Nov 2005, Jim C. Nasby wrote: > On Tue, Nov 22, 2005 at 01:38:34PM -0500, Bruce Momjian wrote: > > Gavin Sherry wrote: > > > > Related question: are there plans afoot to allow specifying an alternate > > > > location for pg_xlog (or pg_delete-me-not) to save doing the > > > > shutdown-

Re: [HACKERS] tablespaces and non-empty directories

2005-11-22 Thread Jim C. Nasby
On Tue, Nov 22, 2005 at 01:38:34PM -0500, Bruce Momjian wrote: > Gavin Sherry wrote: > > > Related question: are there plans afoot to allow specifying an alternate > > > location for pg_xlog (or pg_delete-me-not) to save doing the shutdown-DB, > > > mv > > > directory to other disk, symlink, start

Re: [HACKERS] tablespaces and non-empty directories

2005-11-22 Thread Bruce Momjian
Gavin Sherry wrote: > > Related question: are there plans afoot to allow specifying an alternate > > location for pg_xlog (or pg_delete-me-not) to save doing the shutdown-DB, mv > > directory to other disk, symlink, start-DB dance? > > People have discussed it but I don't know of anyone working on

Re: [HACKERS] tablespaces and non-empty directories

2005-11-17 Thread Tom Lane
"Zeugswetter Andreas DCP SD" <[EMAIL PROTECTED]> 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 mount

Re: [HACKERS] tablespaces and non-empty directories

2005-11-17 Thread Zeugswetter Andreas DCP SD
> > 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; > esp

Re: [HACKERS] tablespaces and non-empty directories

2005-11-16 Thread Tom Lane
Philip Yarra <[EMAIL PROTECTED]> writes: > 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

Re: [HACKERS] tablespaces and non-empty directories

2005-11-16 Thread Gavin Sherry
On Thu, 17 Nov 2005, Philip Yarra wrote: > I assume CREATE TABLESPACE refuses to use a non-empty directory because of the > risk of trashing existing files. Makes sense, but consider the following: Right, that was the reasoning. > > # mkfs -t ext2 /dev/sdc1 > # mount -t ext2 /dev/sdc1 /mnt/pg_ta