Re: tablespaces and non-empty directories - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: tablespaces and non-empty directories
Date
Msg-id 20051123001600.GH7086@pervasive.com
Whole thread Raw
In response to Re: tablespaces and non-empty directories  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: tablespaces and non-empty directories  (Gavin Sherry <swm@linuxworld.com.au>)
Re: tablespaces and non-empty directories  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
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-DB dance?
> > 
> > People have discussed it but I don't know of anyone working on it.
> 
> TODO has:
> 
>     * 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
> do for admins, and it is impossible to do while the server is running.

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?
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461


pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Improving count(*)
Next
From: Gavin Sherry
Date:
Subject: Re: tablespaces and non-empty directories