Re: Configurable path to look up dynamic libraries

Tom Lane writes:

> The point as far as I'm concerned is that paths mentioned in CREATE
> FUNCTION ought to be relative to someplace that's
> installation-dependent. That way, when you dump out and reload a
> CREATE FUNCTION command, the declaration is still good, you just have
> to have put a copy of the function's shlib in the right place for the
> new installation.

Okay, I'm convinced that $libdir can be a useful default. But given the
case where users might want to *add* his directory to the path he needs to
have knowledge of what the default path is. (Unfortunately we can't do
PATH=$PATH:xxx.) Perhaps it would be good to make the empty path
component equivalent to $libdir, e.g.,

'' default, search libdir
':/my/own' search libdir before my own
'/my/own:' search libdir after my own
'/my/own' don't seach libdir

But I think there are enough possibly useful applications for changing
this while the postmaster is running at no real harm.

--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter