Re: WAL file location - Mailing list pgsql-hackers

From Curt Sampson
Subject Re: WAL file location
Date
Msg-id Pine.NEB.4.44.0207302006370.436-100000@angelic.cynic.net
Whole thread Raw
In response to Re: WAL file location  (Thomas Lockhart <lockhart@fourpalms.org>)
Responses Re: WAL file location
Re: WAL file location
List pgsql-hackers
On Mon, 29 Jul 2002, Thomas Lockhart wrote:

> It is supported by the installation environment, and does not require
> the explicit three steps of
>
> 1) creating a new directory area
> 2) moving files to the new area
> 3) creating a symlink to point to the new area

So basically it gives you the ability to initdb and have your log files
elsewhere without having to shutdown, move the log, link, and restart.
Is there anything else it adds?

BTW, you mention in another message that environment variables work
well for you. Well, they are a security problem waiting to happen,
IMHO. Do you have any objections to having a file containing a list
of the various data directories? Maybe we could put the log directory
in it, too, and have PGDATA point to that file, so we'd need only one
environment variable? (And then we'd have a more obviously accessable
list of where everything is, as well.)

I tend to side with you on not putting these paths in the database
itself; it can make restores rather hairy.

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: Curt Sampson
Date:
Subject: Re: Why is MySQL more chosen over PostgreSQL?
Next
From: Peter Eisentraut
Date:
Subject: Re: What exactly does lanispl mean?