| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: config files in /data |
| Date: | 2000-05-31 17:16:30 |
| Message-ID: | 7276.959793390@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:
> 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/ ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2000-05-31 17:18:17 | Re: config files in /data |
| Previous Message | Thomas Lockhart | 2000-05-31 16:26:57 | Re: ODBC patch |