diff options
| author | Peter Eisentraut <peter@eisentraut.org> | 2023-05-05 06:29:49 +0200 |
|---|---|---|
| committer | Peter Eisentraut <peter@eisentraut.org> | 2023-05-05 07:12:18 +0200 |
| commit | 14bb2e76c7df484518226b6e7e4e9476344497cc (patch) | |
| tree | fbec31e12bedfccef7adc72ca8774451504c2f5e /src/backend/executor/nodeBitmapAnd.c | |
| parent | 24964394a972d0e7b030bf02a600bceea0be72d3 (diff) | |
| download | postgresql-14bb2e76c7df484518226b6e7e4e9476344497cc.tar.gz postgresql-14bb2e76c7df484518226b6e7e4e9476344497cc.zip | |
Fix prove_installcheck when used with PGXS
Commit 153e215677 added the portlock directory. This is created in
$ENV{top_builddir} if it is set. Under PGXS, top_builddir points into
the installation directory, which is not necessarily writable and in
any case inappropriate to use by a test suite. The cause of the
problem is that the prove_installcheck target in Makefile.global
exports top_builddir, which isn't useful (since no other Perl code
actually reads it) and breaks this use case. The reason this code is
there is probably that is has been dragged around with various other
changes, in particular a0fc813266, but without a real purpose of its
own. By just removing the exporting of top_builddir in
prove_installcheck, the portlock directory then ends up under
tmp_check in the build directory, which is more suitable.
Reviewed-by: Andrew Dunstan <andrew@dunslane.net>
Discussion: https://www.postgresql.org/message-id/78d1cfa6-0065-865d-584b-cde6d8c18aff@enterprisedb.com
Diffstat (limited to 'src/backend/executor/nodeBitmapAnd.c')
0 files changed, 0 insertions, 0 deletions