Proposed installation dir change - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Proposed installation dir change
Date
Msg-id Pine.LNX.4.30.0109140132140.680-100000@peter.localdomain
Whole thread Raw
List pgsql-hackers
I would like to do the following:  Put the dynamically loadable shared
objects for the language handlers (language handlers being the only shared
objects we install by default) into a private subdirectory
'$(libdir)/postgresql'.  The default directory where the backend looks for
shared objects will point at this location.

Advantages:  Cleaner file system layout, keeps things out of $(libdir).

We can install the contrib modules into that directory without cluttering
the file system. Then we can eliminate hard-coding the path to the contrib
modules because they will be found in the directory by default.

Third-party extension modules can put their files into this directory
without worries about file system clashes.  (I would encourage third-party
products to use their own installation hierarchy, because otherwise
they'll have the same problems as we have with Perl, but it is a
convenient solution nevertheless.)

There should not be any compatibility problems because these files aren't
accessed directly.  The binary packages already do this, because of some
of these concerns.

-- 
Peter Eisentraut   peter_e@gmx.net   http://funkturm.homeip.net/~peter



pgsql-hackers by date:

Previous
From: "Marc G. Fournier"
Date:
Subject: Re: [JDBC] Re: What needs to be done?
Next
From: Rachit Siamwalla
Date:
Subject: Re: ERROR: Cannot insert a duplicate key into a unique