Re: make check For Extensions - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: make check For Extensions
Date
Msg-id alpine.DEB.2.10.1406130808560.30558@sto
Whole thread Raw
In response to Re: make check For Extensions  ("David E. Wheeler" <david@justatheory.com>)
Responses Re: make check For Extensions
List pgsql-hackers
> That does not mean that it starts a new cluster on a port. It means it 
> will test it against an existing cluster after you have installed into 
> that cluster.

Yes, that is what I was saying.

>> It invokes "psql" which is expected to work directly. Note that there 
>> is no temporary installation, it is tested against the installed and 
>> running postgres. Maybe having the ability to create a temporary 
>> installation, as you suggest, would be a nice extension.
>
> Yes, that’s what I would like, so I could test *before* installing.

I would suggest to add that to https://wiki.postgresql.org/wiki/Todo.

I may look into it when I have time, over the summer. The key point is 
that there is no need for a temporary installation, but only of a 
temporary cluster, and to trick this cluster into loading the uninstalled 
extension, maybe by playing with dynamic_library_path in the temporary 
cluster.

-- 
Fabien.

pgsql-hackers by date:

Previous
From: Rajmohan C
Date:
Subject: loading .so file at run time
Next
From: Dean Rasheed
Date:
Subject: Re: API change advice: Passing plan invalidation info from the rewriter into the planner?