From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | teg(at)redhat(dot)com (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=) |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Configurable path to look up dynamic libraries |
Date: | 2001-05-15 19:27:35 |
Message-ID: | 11253.989954855@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
teg(at)redhat(dot)com (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=) writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> teg(at)redhat(dot)com (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=) writes:
> You could search in a path... first sysconfdir, then datadir.
>>
>> Surely the other way around.
> Which could work as well - or just a switch to postmaster to tell it
> which file to use.
I could live with a datadir-then-sysconfdir path search. (It should be
datadir first, since the sysconfdir file would serve as a system-wide
default for multiple postmasters.) Given that approach I see no real
need for a postmaster switch.
Possibly the same approach should apply to all the config files we
currently store in datadir?
There is a security issue here: stuff stored in datadir is not visible
to random other users on the machine (since datadir is mode 700), but
I would not expect sysconfdir to be mode 700. We'd need to think about
the implications of allowing Postgres config files to be world-visible.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Trond Eivind =?iso-8859-1?q?Glomsr=F8d?= | 2001-05-15 19:30:53 | Re: Configurable path to look up dynamic libraries |
Previous Message | Trond Eivind =?iso-8859-1?q?Glomsr=F8d?= | 2001-05-15 19:13:22 | Re: Configurable path to look up dynamic libraries |