| From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "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> |
| Cc: | "mlw" <markw(at)mohawksoft(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Explicit configuration file |
| Date: | 2001-12-12 09:44:00 |
| Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA41EB456@m0114.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Doug McNaught | 2001-12-12 12:03:44 | Re: Explicit configuration file |
| Previous Message | Dave Page | 2001-12-12 08:43:10 | Re: Explicit configuration file |