| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: libpq_pipeline in tmp_install |
| Date: | 2021-05-19 15:06:51 |
| Message-ID: | 3431093.1621436811@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> writes:
> On 10.05.21 20:26, Peter Eisentraut wrote:
>> 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.
> Here is a patch that implements the second solution, which turned out to
> be very easy.
+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).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2021-05-19 15:25:10 | Re: pgbench test failing on 14beta1 on Debian/i386 |
| Previous Message | Justin Pryzby | 2021-05-19 14:39:08 | Re: PG 14 release notes, first draft |