Re: tablespaces and non-empty directories

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, Philip Yarra <philip(at)utiba(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: tablespaces and non-empty directories
Date: 2005-11-23 00:41:14
Message-ID: 20051123004114.GA18494@surnet.cl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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
> > 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?

Hmm, I doubt moving any of the SLRU files (clog, subtrans, multixact)
will have much of an impact. If there's too much I/O on those, a better
solution would be to increase the number of buffers allocated to them.
Currently we use 8 for all of them which is probably not appropiate for
everyone.

Not sure about pg_twophase, but I doubt it's used on a too much
performance critical path (after all, there an awful lot of other work
to do to "prepare" a transaction.)

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Chuck McDevitt 2005-11-23 00:46:01 Re: [PATCHES] Should libedit be preferred to
Previous Message Bruce Momjian 2005-11-23 00:34:57 Re: A few pgindent oddities