aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/postgres_fdw.c
diff options
context:
space:
mode:
authorNoah Misch <noah@leadboat.com>2019-05-28 12:59:00 -0700
committerNoah Misch <noah@leadboat.com>2019-05-28 13:00:26 -0700
commit5c0fee0be2f64439149a37bc4bc4f44b1fcdcda8 (patch)
tree4661e69fb54658ac9b2da76f32e4ea852fc567b3 /contrib/postgres_fdw/postgres_fdw.c
parentf3798089d84e965b4570d4e774afe110d805f8e0 (diff)
downloadpostgresql-5c0fee0be2f64439149a37bc4bc4f44b1fcdcda8.tar.gz
postgresql-5c0fee0be2f64439149a37bc4bc4f44b1fcdcda8.zip
In the pg_upgrade test suite, don't write to src/test/regress.
When this suite runs installcheck, redirect file creations from src/test/regress to src/bin/pg_upgrade/tmp_check/regress. This closes a race condition in "make -j check-world". If the pg_upgrade suite wrote to a given src/test/regress/results file in parallel with the regular src/test/regress invocation writing it, a test failed spuriously. Even without parallelism, in "make -k check-world", the suite finishing second overwrote the other's regression.diffs. This revealed test "largeobject" assuming @abs_builddir@ is getcwd(), so fix that, too. Buildfarm client REL_10, released fifty-four days ago, supports saving regression.diffs from its new location. When an older client reports a pg_upgradeCheck failure, it will no longer include regression.diffs. Back-patch to 9.5, where pg_upgrade moved to src/bin. Reviewed (in earlier versions) by Andrew Dunstan. Discussion: https://postgr.es/m/20181224034411.GA3224776@rfd.leadboat.com
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions