| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Oliver Elphick <olly(at)lfix(dot)co(dot)uk>, Vince Vielhaber <vev(at)michvhf(dot)com>, "J(dot) M(dot) Brenner" <doom(at)kzsu(dot)stanford(dot)edu>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: location of the configuration files |
| Date: | 2003-02-14 20:27:53 |
| Message-ID: | 9285.1045254473@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Tom Lane writes:
>> I would favor a setup that allows a -C *directory* (not file) to be
>> specified as a postmaster parameter separately from the -D directory;
> A directory is not going to satisfy people.
Why not? Who won't it satisfy, and what's their objection?
AFAICS, you can either set -C to /etc if you want your PG config files
loose in /etc, or you can set it to /etc/postgresql/ if you want them
in a privately-owned directory. Which other arrangements are needed?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Curtis Faith | 2003-02-14 20:41:06 | Re: Brain dump: btree collapsing |
| Previous Message | Bruce Momjian | 2003-02-14 20:19:36 | Re: location of the configuration files |