On 2013-06-04 16:07:23 -0400, Tom Lane wrote:
> Andres Freund <andres@2ndquadrant.com> writes:
> > The only argument with a good bit of merit I can see is that it could
> > lead to unexpected extensions being loaded if e.g. hstore isn't
> > installed in the normal extension directory but another extension with
> > the same name somewhere else.
>
> And just think about the fun you could have with inconsistent files
> named hstore--1.0--1.1.sql in different directories. The extension
> feature is really really not designed to be able to search a path of
> directories.
Well, some definitional work would be needed. That specific problem
seems sensibl solveable by defineing those to be relative to the control
file.
I don't really care much about Oliver's usecase TBH, but I would very much
welcome making it easier for application developers to package part of
ther in-database application code as extensions without either requiring
a selfcompiled postgres with a custom extension dir or them having have
root access to the machine running postgres.
Providing them with access to a directory that's only configured as
additional extension directory for a development cluster would be a huge
improvement.
Greetings,
Andres Freund
-- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services
