From: | Andrew Sullivan <andrew(at)libertyrms(dot)info> |
---|---|
To: | PostgreSQL Hackers List <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WAL file location |
Date: | 2002-07-30 16:45:50 |
Message-ID: | 20020730124550.B13729@mail.libertyrms.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jul 30, 2002 at 08:10:02PM +0900, Curt Sampson wrote:
> 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 guess I'm dumb, but I'm not seeing how these environment variables
are a big security risk. It's true, however, that putting such
settings in the config file or something might be better, if only
because that limits the number of places where various config things
happen.
In any case, it'd be a _very good_ thing to have a tablespace-like
facility. Its lack is a real drawback of PostgreSQL for anyone
looking to manage a large installation. RAID is your friend, of
course, but one can get a real boost to both performance and
flexibility by adding this sort of feature, and anything that moves
PostgreSQL closer to such a goal is, in my view, nothing but a good
thing.
A
--
----
Andrew Sullivan 87 Mowat Avenue
Liberty RMS Toronto, Ontario Canada
<andrew(at)libertyrms(dot)info> M6K 3E3
+1 416 646 3304 x110
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-07-30 16:47:46 | Re: SET LOCAL again |
Previous Message | Tom Lane | 2002-07-30 16:44:57 | Re: SET LOCAL again |