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

From Gavin Sherry
Subject Re: tablespaces and non-empty directories
Date
Msg-id Pine.LNX.4.58.0511231119130.25942@linuxworld.com.au
Whole thread Raw
In response to Re: tablespaces and non-empty directories  ("Jim C. Nasby" <jnasby@pervasive.com>)
Responses Re: tablespaces and non-empty directories  (Philip Yarra <philip@utiba.com>)
List pgsql-hackers
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-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?

pgsql_tmp

Gavin


pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: tablespaces and non-empty directories
Next
From: Bruce Momjian
Date:
Subject: Re: A few pgindent oddities