Re: WAL file location
Bruce Momjian <pgman@candle.pha.pa.us>
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Lamar Owen <lamar.owen@wgcr.org>,
Andrew Sullivan <andrew@libertyrms.info>, Thomas Lockhart <lockhart@fourpalms.org>, PostgreSQL Hackers List <pgsql-hackers@postgresql.org>
Date: 2002-07-30T20:20:08Z
Lists: pgsql-hackers
Tom Lane wrote: > Lamar Owen <lamar.owen@wgcr.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@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026