libpq_pipeline in tmp_install

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема libpq_pipeline in tmp_install
Дата
Msg-id cb9d16a6-760f-cd44-28d6-b091d5fb6ca7@enterprisedb.com
обсуждение исходный текст
Ответы Re: libpq_pipeline in tmp_install  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Список pgsql-hackers
The test program libpq_pipeline produced by the test suite in 
src/test/modules/libpq_pipeline/ is installed into tmp_install as part 
of make check.  This isn't a real problem by itself, but I think it 
creates a bit of an asymmetric situation that might be worth cleaning up.

Before, the contents of tmp_install exactly matched an actual 
installation.  There were no extra test programs installed.

Also, the test suite code doesn't actually use that installed version, 
so it's not of any use, and it creates confusion about which copy is in use.

The reason this is there is that the test suite uses PGXS to build the 
test program, and so things get installed automatically.  I suggest that 
we should either write out the build system by hand to avoid this, or 
maybe extend PGXS to support building programs but not installing them. 
The advantage of the former approach is that it would allow additional 
test programs to be added later as well.  (We should really collect the 
libpq tests under src/interfaces/libpq/ anyway at some point.)



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: Reducing opr_sanity test's runtime under CLOBBER_CACHE_ALWAYS
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Another modest proposal for reducing CLOBBER_CACHE_ALWAYS runtime