From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Trond Eivind Glomsrød <teg(at)redhat(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Configurable path to look up dynamic libraries |
Date: | 2001-05-15 19:45:22 |
Message-ID: | Pine.LNX.4.30.0105152140570.757-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Trond Eivind Glomsrød 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.
Might as well use a symlink in this case.
I could go for a solution that processed both files in order (possibly
even ${sysconfdir}/postgresql.conf, $PGDATA/postgresql.conf,
${sysconfdir}/postgresql.conf.fixed in order, à la PINE). It could be as
easy as adding two or three lines in postmaster.c. However, I'm afraid
users will interpret a file in $sysconfdir as something clients should
process as well, which is not part of this deal.
--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter
From | Date | Subject | |
---|---|---|---|
Next Message | Trond Eivind =?iso-8859-1?q?Glomsr=F8d?= | 2001-05-15 19:47:00 | Re: Configurable path to look up dynamic libraries |
Previous Message | Tom Lane | 2001-05-15 19:43:00 | Re: Configurable path to look up dynamic libraries |