Re: libpq_pipeline in tmp_install

Поиск
Список
Период
Сортировка
Искать
От
Peter Eisentraut
Тема
Re: libpq_pipeline in tmp_install
Дата
в 09:04:40
Msg-id
82fb186d-f336-b981-0ea3-20e1197a0864@enterprisedb.com
Ответ на
Список
Дерево обсуждения
libpq_pipeline in tmp_install Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: libpq_pipeline in tmp_install Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: libpq_pipeline in tmp_install Tom Lane <tgl@sss.pgh.pa.us>
Re: libpq_pipeline in tmp_install Alvaro Herrera <alvherre@alvh.no-ip.org>
Re: libpq_pipeline in tmp_install Tom Lane <tgl@sss.pgh.pa.us>
Re: libpq_pipeline in tmp_install Peter Eisentraut <peter.eisentraut@enterprisedb.com>
On 19.05.21 19:35, Tom Lane wrote:
> Alvaro Herrera  writes:
>> On 2021-May-19, Tom Lane wrote:
>>> +1, except that you should add documentation for NO_INSTALL to the
>>> list of definable symbols at the head of pgxs.mk, and to the list
>>> in extend.sgml (compare that for NO_INSTALLCHECK).
> 
>> I propose this.
> 
> WFM.

Thanks for the feedback.  I found that my proposal doesn't quite work, 
because "check" doesn't depend on "all" (anymore; see dbf2ec1a1c0), so 
running make check-world doesn't build the test program first.  The 
easiest workaround I found was to add an "install: all" line even for 
the NO_INSTALL case.  It's all a bit hackish, though.
В списке pgsql-hackers по дате отправления
От: Dilip Kumar
Дата:
От: tanghy.fnst@fujitsu.com
Дата:
FAQ