Re: WAL file location

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>, Andrew Sullivan <andrew(at)libertyrms(dot)info>, Thomas Lockhart <lockhart(at)fourpalms(dot)org>, PostgreSQL Hackers List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WAL file location
Date: 2002-07-30 20:20:08
Message-ID: 200207302020.g6UKK8619665@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> writes:
> > Having said all that, I still believe that this is something tailor-made for
> > postgresql.conf.
>
> Well, exactly. Regardless of how serious you may think the security
> argument is, it still remains that a config-file entry seems the ideal
> way to do it. I can't see any good argument in favor of relying on
> environment variables instead. They don't bring any new functionality
> to the party; and we have an awful lot of work invested in putting all
> sorts of functionality into the GUC module. I think that doing
> configuration-like stuff outside the GUC framework is now something that
> we should resist --- or at least have a darn good reason for it when we
> do it.

Thomas, are you going to extend this to locations for any table/index?
Seems whatever we do for WAL should fix in that scheme.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-07-30 20:21:24 Re: [GENERAL] Stats Collector
Previous Message Tom Lane 2002-07-30 20:17:51 Re: WAL file location