Re: Configurable path to look up dynamic libraries - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Configurable path to look up dynamic libraries
Date
Msg-id Pine.LNX.4.30.0105152140570.757-100000@peter.localdomain
Whole thread Raw
In response to Re: Configurable path to look up dynamic libraries  (teg@redhat.com (Trond Eivind Glomsrød))
List pgsql-hackers
Trond Eivind Glomsrød writes:

> Tom Lane <tgl@sss.pgh.pa.us> writes:
>
> > teg@redhat.com (Trond Eivind Glomsrød) 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@gmx.net   http://funkturm.homeip.net/~peter



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Configurable path to look up dynamic libraries
Next
From: Tom Lane
Date:
Subject: Re: Configurable path to look up dynamic libraries