aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistbuildbuffers.c
diff options
context:
space:
mode:
authorPeter Eisentraut <peter@eisentraut.org>2023-05-05 06:29:49 +0200
committerPeter Eisentraut <peter@eisentraut.org>2023-05-05 07:10:30 +0200
commite0702250040437e314779babcc417d7448a1f017 (patch)
tree47947d2791e4e2606614fa2d4dd00faec32d29f7 /src/backend/access/gist/gistbuildbuffers.c
parent52c9cf3239b85f272d928db178d44947c9173d76 (diff)
downloadpostgresql-e0702250040437e314779babcc417d7448a1f017.tar.gz
postgresql-e0702250040437e314779babcc417d7448a1f017.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/access/gist/gistbuildbuffers.c')
0 files changed, 0 insertions, 0 deletions