Re: make check For Extensions

Поиск
Список
Период
Сортировка
От Fabien COELHO
Тема Re: make check For Extensions
Дата
Msg-id alpine.DEB.2.10.1406130808560.30558@sto
обсуждение исходный текст
Ответ на Re: make check For Extensions  ("David E. Wheeler" <david@justatheory.com>)
Ответы Re: make check For Extensions
Список 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 по дате отправления:

Предыдущее
От: Rajmohan C
Дата:
Сообщение: loading .so file at run time
Следующее
От: Dean Rasheed
Дата:
Сообщение: Re: API change advice: Passing plan invalidation info from the rewriter into the planner?