Re: [COMMITTERS] pgsql-server/src backend/tcop/postgres.cbacke - Mailing list pgsql-hackers

From Curt Sampson
Subject Re: [COMMITTERS] pgsql-server/src backend/tcop/postgres.cbacke
Date
Msg-id Pine.NEB.4.44.0208151303040.1718-100000@angelic.cynic.net
Whole thread Raw
In response to Re: [COMMITTERS] pgsql-server/src backend/tcop/postgres.cbacke  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: [COMMITTERS] pgsql-server/src backend/tcop/postgres.cbacke  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
On Thu, 15 Aug 2002, Bruce Momjian wrote:

> I would like to know how to move this item forward.

Right now (i.e., in 7.2), the only two options we have for moving the
log file to a different spindle are mounting it on pg_xlog and using a
symlink. I doubt many people do the the former, and if they do they do
not need an option to init_db to move the logfile away from its default
location.

So I propose we just continue to use the symlink method for the moment,
until we agree on another way to store the log file location within the
data directory, and at that time we implement the code to do that.

Note that if we don't move forward at all, we're still left in the symlink
situation, with the exception that you init_db, move the log directory and
create the symlink by hand, and then start up the database. So this partial
move forward makes no difference to the symlink argument.

cjs
-- 
Curt Sampson  <cjs@cynic.net>   +81 90 7737 2974   http://www.netbsd.org   Don't you know, in this new Dark Age, we're
alllight.  --XTC
 



pgsql-hackers by date:

Previous
From: "Christopher Kings-Lynne"
Date:
Subject: Re: Open 7.3 issues
Next
From: Neil Conway
Date:
Subject: Re: Open 7.3 issues