Lamar wrote:
> > I would like postgresql.conf to not 
> > get overwritten if I have to re-initdb.

This is something I would also like. 

Bruce wrote:
> I wonder if we should go one step further.  Should we be specifying the
> config file on the command line _rather_ than the data directory. We
> could then specify the data directory location in the config file.  That
> seems like the direction we should be headed in, though I am not sure it
> is worth the added headache of the switch.

Yes, I vote for a -C switch for postmaster (postmaster -C /etc/postgresql.conf)
and inclusion of PGDATA in postgresql.conf .
Maybe even a new envvar PGCONFIG that a la long replaces PGDATA.

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 ...).

Andreas

Wed, 12 Dec 2001 10:44:00 +0100
"Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at>
Re: Explicit configuration file
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@gmx.net


Wed, 12 Dec 2001 23:26:33 +0100 (CET)
Peter Eisentraut <peter_e@gmx.net>
Re: Explicit configuration file