| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at> |
| Cc: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>, <lockhart(at)fourpalms(dot)org>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, mlw <markw(at)mohawksoft(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Explicit configuration file |
| Date: | 2001-12-12 22:26:33 |
| Message-ID: | Pine.LNX.4.30.0112121800030.627-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Zeugswetter Andreas SB SD writes:
> Imho PGDATA does not really have a future anyway with tablespaces coming,
> and multiple directories where pgdata lives (root on hdisk1, pg_xlog on
> hdisk2 ...).
Probably true. The question is where the table space setup is going to be
configured. (Some of it will be done within the system catalogs, but the
log directories, etc. need to be configured externally.) If the answer is
postgresql.conf then I don't think that's a good idea because it would
make it impossible to use the same postgresql.conf for multiple servers.
I guess that's impossible already because the port is configured there,
but it *should* be possible, because else why would you want to have it in
a global location.
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert E. Bruccoleri | 2001-12-12 22:29:04 | Regression test database is not working |
| Previous Message | Peter Eisentraut | 2001-12-12 22:25:41 | Re: Explicit configuration file |