aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/postgres_fdw.c
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2017-03-15 19:03:29 -0700
committerAndres Freund <andres@anarazel.de>2017-03-15 19:03:29 -0700
commit2038bf41c963f9ec626f7f8f1f03f0471d063b6d (patch)
treee0d30fa5055468a66b9c6c8bce84da206ff822a2 /contrib/postgres_fdw/postgres_fdw.c
parentbd1827c7c961568eabe850df254c60d175bec195 (diff)
downloadpostgresql-2038bf41c963f9ec626f7f8f1f03f0471d063b6d.tar.gz
postgresql-2038bf41c963f9ec626f7f8f1f03f0471d063b6d.zip
Specify bindir in pg_isolation_regress_installcheck.
It appears dcae5faccab64776376d3 forgot to add it to pg_isolation_regress_installcheck, while it was added to pg_regress_installcheck. It seems to so far have escaped notice, because buildfarm animals requiring it, didn't actually use pg_isolation_regress_installcheck anywhere - that changed with 60f826c5e6244, triggering failures on narwhal and frogmouth. I've decided to not, for now at least, backpatch this, because the relevant invocations look quite different in the back branches. Seems quite possible that we'll want to backport 60f826c5e6244 as a whole if it proves stable. Discussion: https://postgr.es/m/20170315174003.3dyl4teashdwgblh@alap3.anarazel.de
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions