From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: config files in /data |
Date: | 2000-05-31 17:18:17 |
Message-ID: | 200005311718.NAA10742@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Bruce Momjian writes:
> >> Seems we should have pg_hba.conf and other files in a separate
> >> directory, not /data.
>
> > I think the internal files, such as pg_control should be in data/base/
> > instead, so as to not mix them up with user-editable files such as
> > pg_hba.conf, `configuration' (as of 3 min ago), ident, and password files.
>
> Doesn't that pose a risk of collision with user-chosen database names?
> Rather than restricting database names, we should keep these files in
> a different subdirectory. I agree that it's a good idea to separate
> them from the directly-editable config files, just not to put them in
> data/base/ ...
Yes, seems user-editable files should go in pgsql/etc or pgsql/config.
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-05-31 17:23:57 | Re: config files in /data |
Previous Message | Tom Lane | 2000-05-31 17:16:30 | Re: config files in /data |